From Fedora Project Wiki

(Created page with '{{QA/Test_Case |description=This test case tests the functionality of the ABRT feature. |actions= # We will check that the ''abrt-cli'' works and provides meani...')
 
(updated the workflow for the new abrt-cli)
Line 4: Line 4:
# We will check that the ''abrt-cli'' works and provides meaningful information
# 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 ''abrt'' daemon is running
# Mind ''abrtd'' daemon is running
# First investigate them via ''abrt-gui'' -- which packages crashed, when, version, etc.
# First investigate them via ''abrt-gui'' -- which packages crashed, when, version, etc.
# Run <pre>abrt-cli --get-list-full</pre> in terminal
# Run <pre>abrt-cli --get-list-full</pre> in terminal to show all crashes.
# Run <pre>abrt-cli --get-list</pre>
# Run <pre>abrt-cli --get-list</pre> to show unreported crashes.
# Run <pre>abrt-cli --report <uuid></pre> to report the crash
# 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></pre> to report the crash without confirming
# 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></pre> to delete item with UUID <uuid>
# 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 '''--get-list-full''' shows all crashes
Line 16: Line 16:
# Option '''--report''' shows crash report and asks for confirmation before sending it
# Option '''--report''' shows crash report and asks for confirmation before sending it
# Option '''--report-always''' sends crash report
# Option '''--report-always''' sends crash report
# Option '''--delete''' deletes crash with UUID <uuid>
# Option '''--delete''' deletes crash
}}
}}
[[Category:ABRT_Test_Cases]]
[[Category:ABRT_Test_Cases]]

Revision as of 13:05, 30 March 2010

Description

This test case tests the functionality of the ABRT feature.


How to test

  1. We will check that the abrt-cli works and provides meaningful information
  2. After running previous ABRT test cases you probably have a bunch of crash reports in cache. If not do some crashing: 
    kill -SIGSEGV (pid)
  3. Mind abrtd daemon is running
  4. First investigate them via abrt-gui -- which packages crashed, when, version, etc.
  5. Run 
    abrt-cli --get-list-full
    in terminal to show all crashes.
  6. Run 
    abrt-cli --get-list
    to show unreported crashes.
  7. Run 
    abrt-cli --report <uuid>
    to report the crash. You can also refer to a crash using its ordinal number, prefixed by the at sign. Enter 
    abrt-cli --report @0
    to report the first crash from the list, 
    abrt-cli --report @1
    to report the second one et cetera.

    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 to report or N to skip reporting.

  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
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_CLI&oldid=162420"