QA:Testcase ABRT CLI

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(convert to new category system)
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] command line interface.  
+
 
 +
|description=This test case tests the functionality of the ABRT command line interface.  
 +
 
 +
|setup=
 +
# If you are running through the set of ABRT test cases you probably have a bunch of crash reports in cache. If not, then crash some applications with the command {{command|kill -SIGSEGV (pid)}}. Make sure they are not applications containing important data!
 +
# Make sure you have {{package||abrt-cli}} installed: {{command|su -c 'yum install abrt-cli'}}
 
|actions=
 
|actions=
# After running previous ABRT test cases you probably have a bunch of crash reports in cache. If not do some crashing with the command {{command|kill -SIGSEGV (pid)}}
+
# Run {{command|abrt-cli list}} to show unreported crashes
# Check the information on each crash from the graphical front end {{command|abrt-gui}}
+
# Run {{command|abrt-cli list --full}} to show all crashes
# Check whether {{filename|/etc/abrt/plugins/Bugzilla.conf}} and {{filename|~/.abrt/Bugzilla.conf}} contain your Bugzilla login and password. The second file may not exist, which is fine. If these files do contain the information, remove it
+
# Try crash reporting: run {{command|report-cli -e report_Logger -- <tt>DIR</tt>}} to report a crash to e.g. Logger
# Run {{command|abrt-cli --get-list-full}} in terminal to show all crashes
+
#* Select reporting using Logger
# Run {{command|abrt-cli --get-list}} to show unreported crashes
+
# Run {{command|abrt-cli rm <tt>DIR</tt>}} to delete the report
# Try crash reporting: run {{command|abrt-cli --report (uid):(uuid)}} to report a crash, identifying it via UID:UUID pair. UIDs and UUIDs can be found in --get-list[-full] output
+
## ABRT should analyze the crash and creates a report about it. This might take a while. When the report is ready, {{command|abrt-cli}} should open a text editor with the content of the report. You can see what is being reported, and you can fill in instructions on how to reproduce the crash and other comments. When you are done with the report, save your changes and close the editor
+
## You should be asked if you want to report using some reporter plugins. Respond ''Y'' for Bugzilla reporter, and ''N'' to skip reporting using Logger
+
## When reporting via Bugzilla plugin, ''abrt-cli'' should ask for login and password
+
# Create {{filename|~/.abrt/Bugzilla.conf}} with the contents:
+
#:<pre>
+
#:Login=your@email.org
+
#:Password=yourpassword
+
#:</pre>
+
# Try the crash reporting again, this time using {{command|abrt-cli --report @(x)}} to report a crash using its ordinal number (x). This time {{command|abrt-cli}} should take your login and password from the configuration file instead of asking you
+
# Run {{command|abrt-cli --report-always (uuid-or-@x)}} to report a crash without confirming, using all reporters associated with the crash
+
# Run {{command|abrt-cli --delete (uuid-or-@x)}} to delete the report with the chosen UUID or ordinal number
+
 
|results=
 
|results=
# Option '''--get-list-full''' should show all crashes
+
# Option '''list''' shows all not-yet-reported crashes
# Option '''--get-list''' should show all not-yet-reported crashes
+
# Option '''list --full''' shows all crashes
# Option '''--report''' should show crash report and asks for confirmation before sending it
+
# Option '''report''' shows crash report and asks for confirmation before sending it
# Option '''--report-always''' should send crash report
+
#* ABRT asks you to choose one of the analyzer 'local GDB debugger' or 'retrace sever' and then analyzes the crash and creates a report. When the report is ready, {{command|abrt-cli}} opens a text editor with the content of the report. You can see what's being reported, and you are able to fill in instructions on how to reproduce the crash and other comments.
# Option '''--delete''' should delete crash
+
#* You are asked if you want to execute some reporter plugins or not.
 +
# Option '''rm''' deletes crash
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Latest revision as of 13:25, 7 May 2013

Contents

Description

This test case tests the functionality of the ABRT command line interface.

Setup

  1. If you are running through the set of ABRT test cases you probably have a bunch of crash reports in cache. If not, then crash some applications with the command kill -SIGSEGV (pid). Make sure they are not applications containing important data!
  2. Make sure you have Package-x-generic-16.pngabrt-cli installed: su -c 'yum install abrt-cli'

How to test

  1. Run abrt-cli list to show unreported crashes
  2. Run abrt-cli list --full to show all crashes
  3. Try crash reporting: run report-cli -e report_Logger -- DIR to report a crash to e.g. Logger
    • Select reporting using Logger
  4. Run abrt-cli rm DIR to delete the report

Expected Results

  1. Option list shows all not-yet-reported crashes
  2. Option list --full shows all crashes
  3. Option report shows crash report and asks for confirmation before sending it
    • ABRT asks you to choose one of the analyzer 'local GDB debugger' or 'retrace sever' and then analyzes the crash and creates a report. When the report is ready, abrt-cli opens a text editor with the content of the report. You can see what's being reported, and you are able to fill in instructions on how to reproduce the crash and other comments.
    • You are asked if you want to execute some reporter plugins or not.
  4. Option rm deletes crash