From Fedora Project Wiki

(convert to new category system)
Line 23: Line 23:
 
# A bug entry should be filed in Bugzilla, the entry should be assigned to the package you crashed, and the traceback of the crash should be attached
 
# A bug entry should be filed in Bugzilla, the entry should be assigned to the package you crashed, and the traceback of the crash should be attached
 
}}
 
}}
[[Category:ABRT_Test_Cases]]
+
[[Category:Package_abrt_test_cases]]

Revision as of 16:16, 13 January 2011

Description

This test case tests that ABRT's ability to report crashes to Bugzilla works correctly.


How to test

  1. If you don't have an account on Bugzilla, create one.
  2. Edit /etc/abrt/abrt.conf and ensure the Bugzilla plugin is listed on the CCpp and Python lines. For example:
    ...
    CCpp = Bugzilla
    Python = Bugzilla
    ...
  3. Restart ABRT with the command su -c 'service abrtd restart'
  4. Ensure that the abrtd and abrt-applet processes are both running
  5. Kill a running process with the command kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  6. Click on the Report button in popup bubble applet to start abrt-gui
  7. Select the entry matching the recently crashed application, click Report
  8. Click on Bugzilla button
  9. Check the box marked "I checked backtrace and removed sensitive data (password, etc)" - after checking, of course
  10. At the report window, click Send report
  11. Enter your Bugzilla account information if prompted for it; if you have not already configured abrt to know your username and password, you should be

Expected Results

  1. A popup message should appear, with information and a link to the reported bug
  2. A bug entry should be filed in Bugzilla, the entry should be assigned to the package you crashed, and the traceback of the crash should be attached