From Fedora Project Wiki

(updated the workflow for the new abrt-cli)
 
(17 intermediate revisions by 8 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 'dnf install abrt-cli'}}
 
|actions=
 
|actions=
# We will check that the ''abrt-cli'' works and provides meaningful information
+
# Run {{command|abrt-cli list}} to show all 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 --not-reported}} to show not reported crashes
# Mind ''abrtd'' daemon is running
+
# Enable Mailx an Logger workflows <pre>sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_logger.conf /etc/libreport/workflows.d/report_mailx.conf</pre>
# First investigate them via ''abrt-gui'' -- which packages crashed, when, version, etc.
+
# Try crash reporting: run {{command|abrt-cli report -- <tt>DIR</tt>}} to e.g. ''Export the problem data information to a text file''
# Run <pre>abrt-cli --get-list-full</pre> in terminal to show all crashes.
+
#* Select reporting using '''Export the problem data information to a text file'''
# Run <pre>abrt-cli --get-list</pre> to show unreported crashes.
+
# Run {{command|abrt-cli rm <tt>DIR</tt>}} to delete the report
# 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 crashes
# Option '''--get-list''' shows all not-yet-reported crashes
+
# Option '''list --not-reported''' shows all not reported crashes
# Option '''--report''' shows crash report and asks for confirmation before sending it
+
# Option '''report''' shows asks for selection of the reporting workflow
# Option '''--report-always''' sends crash report
+
#* ABRT asks you to choose one of the workflows and the ask you whether you want to generate backtrace on the Retrace server or the local machine and then analyzes the crash and creates a report. When the report is ready, {{command|abrt-cli}} ask you for a path to store the report and then 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
+
# Option '''rm''' deletes crash
 
}}
 
}}
[[Category:ABRT_Test_Cases]]
+
[[Category:Package_abrt_test_cases]]

Latest revision as of 07:53, 15 April 2015

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 'dnf install abrt-cli'

How to test

  1. Run abrt-cli list to show all crashes
  2. Run abrt-cli list --not-reported to show not reported crashes
  3. Enable Mailx an Logger workflows
    sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_logger.conf /etc/libreport/workflows.d/report_mailx.conf
  4. Try crash reporting: run abrt-cli report -- DIR to e.g. Export the problem data information to a text file
    • Select reporting using Export the problem data information to a text file
  5. Run abrt-cli rm DIR to delete the report

Expected Results

  1. Option list shows all crashes
  2. Option list --not-reported shows all not reported crashes
  3. Option report shows asks for selection of the reporting workflow
    • ABRT asks you to choose one of the workflows and the ask you whether you want to generate backtrace on the Retrace server or the local machine and then analyzes the crash and creates a report. When the report is ready, abrt-cli ask you for a path to store the report and then 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.
  4. Option rm deletes crash