From Fedora Project Wiki

(ABRT 2 updates)
Line 10: Line 10:
 
# Click on the '''Open ABRT''' button in pop-up notification to start ''abrt-gui''
 
# Click on the '''Open ABRT''' button in pop-up notification to start ''abrt-gui''
 
# Select the entry matching the recently crashed application, click '''Open'''
 
# Select the entry matching the recently crashed application, click '''Open'''
# Go thru the process, select '''Retrace Server''' as a analyzer and choose Bugzilla as a reporting plug-in
+
# Go thru the process, and at reporting step, choose Bugzilla as a reporting event
# When asked, enter your Bugzilla account information
+
# Use "Configure Events" button to set up your Bugzilla account information
# Send the crash report to Bugzilla
+
# Proceed to reporting using "Forward"/"Apply" buttons
 +
# If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut-n-pasted from GUI report window, or retrieved from event_log file in problem data directory (such as /var/spool/abrt/ccpp-2011-03-04-15:46:26-22496/event_log).
 +
 
 
|results=
 
|results=
 
# A notification message should appear, with information about the crash and a link to the reported bug
 
# A notification message should appear, with information about the crash and a link to the reported bug
# 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.
  
 
When satisfied with the report, '''close it as not a bug''', please.
 
When satisfied with the report, '''close it as not a bug''', please.
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 12:25, 16 March 2011

Description

  • This test case tests that ABRT's ability to report crashes to Bugzilla works correctly.
  • If you don't have an account on Bugzilla, create one.


How to test

  1. Open /etc/abrt/abrt_event.conf and ensure there's something like thisEVENT=report_Bugzilla analyzer=Python abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf.
  2. If you changed something, restart ABRT with the command su -c 'service abrtd restart'
  3. Ensure that the abrtd and abrt-applet processes are both running
  4. Kill a running process with the command kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  5. Click on the Open ABRT button in pop-up notification to start abrt-gui
  6. Select the entry matching the recently crashed application, click Open
  7. Go thru the process, and at reporting step, choose Bugzilla as a reporting event
  8. Use "Configure Events" button to set up your Bugzilla account information
  9. Proceed to reporting using "Forward"/"Apply" buttons
  10. If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut-n-pasted from GUI report window, or retrieved from event_log file in problem data directory (such as /var/spool/abrt/ccpp-2011-03-04-15:46:26-22496/event_log).

Expected Results

  1. A notification message should appear, with information about the crash 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.

When satisfied with the report, close it as not a bug, please.