From Fedora Project Wiki

 
(5 intermediate revisions by 5 users not shown)
Line 5: Line 5:
 
|setup=
 
|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!
 
# 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'}}
+
# Make sure you have {{package||abrt-cli}} installed: {{command|su -c 'dnf install abrt-cli'}}
 
|actions=
 
|actions=
# Run {{command|abrt-cli --list}} to show unreported crashes
+
# Run {{command|abrt-cli list}} to show all crashes
# Run {{command|abrt-cli --list --full}} to show all crashes
+
# Run {{command|abrt-cli list --not-reported}} to show not reported crashes
# Try crash reporting: run {{command|abrt-cli --report <tt>CRASH_DIR</tt>}} to report a crash to e.g. Logger
+
# 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>
# Run {{command|abrt-cli --delete <tt>CRASH_DIR</tt>}} to delete the report
+
# Try crash reporting: run {{command|abrt-cli report -- <tt>DIR</tt>}} 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 {{command|abrt-cli rm <tt>DIR</tt>}} to delete the report
 
|results=
 
|results=
# Option '''--list --full''' should show all crashes
+
# Option '''list''' shows all crashes
# Option '''--list''' should show all not-yet-reported crashes
+
# Option '''list --not-reported''' shows all not reported crashes
# Option '''--report''' should show crash report and asks for confirmation before sending it
+
# Option '''report''' shows asks for selection of the reporting workflow
#* 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 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.
#* 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
+
# Option '''rm''' deletes crash
# Option '''--delete''' should delete crash
 
 
}}
 
}}
 
[[Category:Package_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