From Fedora Project Wiki

 
(12 intermediate revisions by 7 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]] command line interface.  
+
 
 +
|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=
# 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}} to show all crashes
# First investigate them via ''abrt-gui'' &mdash; which packages crashed, when, version, etc.
+
# Run {{command|abrt-cli list --not-reported}} to show not reported crashes
# Check that /etc/abrt/plugins/Bugzilla.conf and ~/.abrt/Bugzilla.conf does not contain login and password. ~/.abrt/Bugzilla.conf might not even exist if you didn't create it.
+
# 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 <pre>abrt-cli --get-list-full</pre> in terminal to show all crashes.
+
# 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</pre> to show unreported crashes.
+
#* Select reporting using '''Export the problem data information to a text file'''
# Try crash reporting: run <pre>abrt-cli --report <uid>:<uuid></pre> to report a crash, identifying it via UID:UUID pair. UIDs and UUIDs can be found in --get-list[-full] output.
+
# Run {{command|abrt-cli rm <tt>DIR</tt>}} to delete the report
## 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. 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'' for Bugzilla reporter, and ''N'' to skip reporting using Logger.
 
## When reporting via Bugzilla plugin, ''abrt-cli'' should ask for login and password.
 
# Create ~/.abrt/Bugzilla.conf:
 
#: <code>Login=your@email.org</code>
 
#: <code>Password=yourpassword</code>
 
# Try the crash reporting again, this time using <pre>abrt-cli --report @<x></pre> to report a crash using its ordinal number <x>. This time ''abrt-cli'' takes your login and password from the configuration file instead of asking you.
 
# Another short form is <pre>abrt-cli --report <uuid_prefix></pre>. Prefix must be unique, otherwise abrt-cli will complain.
 
# 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