From Fedora Project Wiki

(minor cleanups)
Line 4: Line 4:
 
* If you don't have an account on [https://bugzilla.redhat.com Bugzilla], [https://bugzilla.redhat.com/createaccount.cgi create] one.
 
* If you don't have an account on [https://bugzilla.redhat.com Bugzilla], [https://bugzilla.redhat.com/createaccount.cgi create] one.
 
|actions=
 
|actions=
# Open {{filename|/etc/abrt/abrt_event.conf}} and ensure there's something like this <tt>EVENT=report_Bugzilla analyzer=Python      abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf</tt>.
+
# Check that the file {{filename|/etc/abrt/abrt_event.conf}} contains a line similar to <tt>EVENT=report_Bugzilla analyzer=Python      abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf</tt>. This is the default, so if you are running a clean system, it should
# If you changed something, restart ABRT with the command {{command|su -c 'service abrtd restart'}}
+
# If you had to edit the file, restart ABRT with the command {{command|su -c 'systemctl restart abrtd.service'}}
 
# Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running
 
# Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running
 
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package
 
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package
Line 14: Line 14:
 
# Use "Configure Events" button in the same window to set up your Bugzilla account information
 
# Use "Configure Events" button in the same window to set up your Bugzilla account information
 
# Proceed to reporting using "Forward"/"Apply" buttons
 
# 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).
+
# If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from the GUI report window, or retrieved from event_log file in problem data directory (e.g. {{filename|/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.
+
After completing this test case, please '''close the bug as NOTABUG'''.
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 17:16, 29 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. Check that the file /etc/abrt/abrt_event.conf contains a line similar to EVENT=report_Bugzilla analyzer=Python abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf. This is the default, so if you are running a clean system, it should
  2. If you had to edit the file, restart ABRT with the command su -c 'systemctl restart abrtd.service'
  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. Write "ABRT2 testing, please disregard" in problem description
  8. At reporting step, choose Bugzilla as a reporting event
  9. Use "Configure Events" button in the same window to set up your Bugzilla account information
  10. Proceed to reporting using "Forward"/"Apply" buttons
  11. If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from the GUI report window, or retrieved from event_log file in problem data directory (e.g. /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

After completing this test case, please close the bug as NOTABUG.