QA:Testcase ABRT CLI

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 10: Line 10:
 
# 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|abrt-cli --report <tt>CRASH_DIR</tt>}} to report a crash to e.g. Logger
 +
#* Respond ''Y'' for Bugzilla reporter, and ''N'' to skip reporting using Logger
 
# Run {{command|abrt-cli --delete <tt>CRASH_DIR</tt>}} to delete the report
 
# Run {{command|abrt-cli --delete <tt>CRASH_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 ask you to choose one of the analyzer 'local GDB debugger' or 'retrace sever' and then 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 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 '''--delete''' deletes crash
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 11:57, 1 April 2011

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 abrt-cli --report CRASH_DIR to report a crash to e.g. Logger
    • Respond Y for Bugzilla reporter, and N to skip reporting using Logger
  4. Run abrt-cli --delete CRASH_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 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 --delete deletes crash