QA:Testcase ABRT CLI

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(abrt-cli asking for Bugzilla password)
(step-by-step)
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 [[Features/ABRT|ABRT]] command line interface.  
 
|actions=
 
|actions=
# We will check that the ''abrt-cli'' works and provides meaningful information
 
 
# 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>
 
# 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>
 
# Mind ''abrtd'' daemon is running
 
# Mind ''abrtd'' daemon is running
Line 8: Line 7:
 
# Run <pre>abrt-cli --get-list-full</pre> in terminal to show all crashes.
 
# Run <pre>abrt-cli --get-list-full</pre> in terminal to show all crashes.
 
# Run <pre>abrt-cli --get-list</pre> to show unreported crashes.
 
# 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.</p><p>When reporting via Bugzilla plugin, ''abrt-cli'' should ask for login and password when those are not set in /etc/abrt/plugins/Bugzilla.conf or ~/.abrt/Bugzilla.conf</p>
+
# Try crash reporting: run <pre>abrt-cli --report <uuid></pre> to report a crash using its UUID.  
 +
## 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. Try to respond ''Y'' to report, and ''N'' to skip reporting.
 +
## When reporting via Bugzilla plugin, ''abrt-cli'' should ask for login and password when those are not set in /etc/abrt/plugins/Bugzilla.conf or ~/.abrt/Bugzilla.conf
 +
# Try the crash reporting again, this time using <pre>abrt-cli --report @<x></pre> to report a crash using its ordinal number <x>
 
# 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 --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
 
# Run <pre>abrt-cli --delete <uuid-or-@x></pre> to delete item with chosen UUID or ordinal number

Revision as of 13:25, 31 March 2010

Description

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


How to test

  1. After running previous ABRT test cases you probably have a bunch of crash reports in cache. If not do some crashing:
    kill -SIGSEGV (pid)
  2. Mind abrtd daemon is running
  3. First investigate them via abrt-gui — which packages crashed, when, version, etc.
  4. Run
    abrt-cli --get-list-full
    in terminal to show all crashes.
  5. Run
    abrt-cli --get-list
    to show unreported crashes.
  6. Try crash reporting: run
    abrt-cli --report <uuid>
    to report a crash using its UUID.
    1. 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.
    2. You will be asked if you want to report using some reporter plugin. Try to respond Y to report, and N to skip reporting.
    3. When reporting via Bugzilla plugin, abrt-cli should ask for login and password when those are not set in /etc/abrt/plugins/Bugzilla.conf or ~/.abrt/Bugzilla.conf
  7. Try the crash reporting again, this time using
    abrt-cli --report @<x>
    to report a crash using its ordinal number <x>
  8. Run
    abrt-cli --report-always <uuid-or-@x>
    to report the crash without confirming, using all reporters associated with the crash
  9. Run
    abrt-cli --delete <uuid-or-@x>
    to delete item with chosen UUID or ordinal number

Expected Results

  1. Option --get-list-full shows all crashes
  2. Option --get-list shows all not-yet-reported crashes
  3. Option --report shows crash report and asks for confirmation before sending it
  4. Option --report-always sends crash report
  5. Option --delete deletes crash