QA:Testcase ABRT CLI

From FedoraProject

Revision as of 05:41, 1 April 2010 by Adamwill (Talk | contribs)

Jump to: navigation, search

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 with the command kill -SIGSEGV (pid)
  2. Check the information on each crash from the graphical front end abrt-gui
  3. Check whether /etc/abrt/plugins/Bugzilla.conf and ~/.abrt/Bugzilla.conf contain your Bugzilla login and password. The second file may not exist, which is fine. If these files do contain the information, remove 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 should analyze the crash and creates a report about it. This might take a while. When the report is ready, 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. When you are done with the report, save your changes and close the editor
    2. 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
    3. When reporting via Bugzilla plugin, abrt-cli should ask for login and password
  7. Create ~/.abrt/Bugzilla.conf with the contents:
    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 should take your login and password from the configuration file instead of asking you
  9. Run abrt-cli --report-always (uuid-or-@x) to report a crash without confirming, using all reporters associated with the crash
  10. Run abrt-cli --delete (uuid-or-@x) to delete the report with the chosen UUID or ordinal number

Expected Results

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