From Fedora Project Wiki

No edit summary
No edit summary
Line 15: Line 15:
#: <code>Password=yourpassword</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.
# 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.
# 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 --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 16:33, 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. First investigate them via abrt-gui — which packages crashed, when, version, etc.
  3. 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.
  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 <uid>:<uuid>
    to report a crash, identifying it via UID:UUID pair. UIDs and UUIDs can be found in --get-list[-full] output.
    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. Respond Y for Bugzilla reporter, and N to skip reporting using Logger.
    3. When reporting via Bugzilla plugin, abrt-cli should ask for login and password.
  7. Create ~/.abrt/Bugzilla.conf:
    Login=your@email.org
    Password=yourpassword
  8. Try the crash reporting again, this time using 
    abrt-cli --report @<x>
    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.
  9. Another short form is 
    abrt-cli --report <uuid_prefix>
    Prefix must be unique, otherwise abrt-cli will complain.
  10. Run 
    abrt-cli --report-always <uuid-or-@x>
    to report the crash without confirming, using all reporters associated with the crash.
  11. 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=162779"