Latest revision as of 07:53, 15 April 2015

Description

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

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!
Make sure you have abrt-cli installed: su -c 'dnf install abrt-cli'

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

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
Run abrt-cli rm DIR to delete the report

Option list shows all crashes
Option list --not-reported shows all not reported crashes
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.
Option rm deletes crash

@@ Line 7: / Line 7: @@
 # Make sure you have {{package||abrt-cli}} installed: {{command|su -c 'dnf install abrt-cli'}}
 |actions=
-# Run {{command|abrt-cli list}} to show crashes
+# Run {{command|abrt-cli list}} to show all crashes
+# Run {{command|abrt-cli list --not-reported}} to show not reported crashes
 # 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>
 # Try crash reporting: run {{command|abrt-cli report -- <tt>DIR</tt>}} to e.g. ''Export the problem data information to a text file''
@@ Line 14: / Line 15: @@
 |results=
 # Option '''list''' shows all crashes
+# Option '''list --not-reported''' shows all not reported crashes
 # 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, {{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.