QA:Testcase ABRT CLI

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(updated the workflow for the new abrt-cli)
 
(14 intermediate revisions by 5 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]] feature.
+
 
 +
|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=
# We will check that the ''abrt-cli'' works and provides meaningful information
+
# Run {{command|abrt-cli list}} to show unreported crashes
# After running previous ABRT test cases you probably have a bunch of crash reports in cache. If not do some crashing: <pre>kill -SIGSEGV (pid)</pre>
+
# Run {{command|abrt-cli list --full}} to show all crashes
# Mind ''abrtd'' daemon is running
+
# Try crash reporting: run {{command|report-cli -e report_Logger -- <tt>DIR</tt>}} to report a crash to e.g. Logger
# First investigate them via ''abrt-gui'' -- which packages crashed, when, version, etc.
+
#* Select reporting using Logger
# Run <pre>abrt-cli --get-list-full</pre> in terminal to show all crashes.
+
# Run {{command|abrt-cli rm <tt>DIR</tt>}} to delete the report
# Run <pre>abrt-cli --get-list</pre> to show unreported crashes.
+
# Run <pre>abrt-cli --report <uuid></pre> to report the crash. You can also refer to a crash using its ordinal number, prefixed by the at sign. Enter <pre>abrt-cli --report @0</pre> to report the first crash from the list, <pre>abrt-cli --report @1</pre> to report the second one et cetera. <p>ABRT analyzes the crash and creates a report about it. This might take a while. When the report is ready, ''abrt-cli'' opens 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.</p><p>When you are done with the report, save your changes and close the editor. You will be asked if you want to report using some reporter plugin. Respond ''Y'' to report or ''N'' to skip reporting.
+
# Run <pre>abrt-cli --report-always <uuid-or-@x></pre> to report the crash without confirming, using all reporters associated with the crash
+
# Run <pre>abrt-cli --delete <uuid-or-@x></pre> to delete item with chosen UUID or ordinal number
+
 
|results=
 
|results=
# Option '''--get-list-full''' shows all crashes
+
# Option '''list''' shows all not-yet-reported crashes
# Option '''--get-list''' shows all not-yet-reported crashes
+
# Option '''list --full''' shows all crashes
# Option '''--report''' shows crash report and asks for confirmation before sending it
+
# Option '''report''' shows crash report and asks for confirmation before sending it
# Option '''--report-always''' sends 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''' deletes crash
+
#* You are asked if you want to execute some reporter plugins or not.
 +
# Option '''rm''' deletes crash
 
}}
 
}}
[[Category: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