QA:Testcase ABRT CLI

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(minor cleanups)
 
(3 intermediate revisions by 3 users not shown)
Line 7: Line 7:
 
# Make sure you have {{package||abrt-cli}} installed: {{command|su -c 'yum install abrt-cli'}}
 
# Make sure you have {{package||abrt-cli}} installed: {{command|su -c 'yum install abrt-cli'}}
 
|actions=
 
|actions=
# Run {{command|abrt-cli --list}} to show unreported crashes
+
# Run {{command|abrt-cli list}} to show unreported crashes
# Run {{command|abrt-cli --list --full}} to show all crashes
+
# Run {{command|abrt-cli list --full}} to show all crashes
# Try crash reporting: run {{command|abrt-cli --report <tt>CRASH_DIR</tt>}} to report a crash to e.g. Logger
+
# 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 --delete <tt>CRASH_DIR</tt>}} to delete the report
+
#* Select reporting using Logger
 +
# Run {{command|abrt-cli rm <tt>DIR</tt>}} to delete the report
 
|results=
 
|results=
# Option '''--list --full''' should show all crashes
+
# Option '''list''' shows all not-yet-reported crashes
# Option '''--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
#* ABRT should analyze the crash and create a report about it. 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. Close the editor
+
#* 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.
#* 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
+
#* You are asked if you want to execute some reporter plugins or not.
# Option '''--delete''' should delete crash
+
# 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