From Fedora Project Wiki

(convert to new category system)
(ABRT 2 updates)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test case tests that [[Features/ABRT|ABRT]]'s ability to report crashes to Bugzilla works correctly.
+
|description=
 +
* This test case tests that ABRT's ability to report crashes to Bugzilla works correctly.
 +
* If you don't have an account on [https://bugzilla.redhat.com Bugzilla], [https://bugzilla.redhat.com/createaccount.cgi create] one.
 
|actions=
 
|actions=
# If you don't have an account on [https://bugzilla.redhat.com Bugzilla], [https://bugzilla.redhat.com/createaccount.cgi create] one.
+
# 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>.
# Edit {{filename|/etc/abrt/abrt.conf}} and ensure the Bugzilla plugin is listed on the ''CCpp'' and ''Python'' lines. For example:
+
# If you changed something, restart ABRT with the command {{command|su -c 'service abrtd restart'}}
#:<pre>
 
#:...
 
#:CCpp = Bugzilla
 
#:Python = Bugzilla
 
#:...
 
#:</pre>
 
# Restart ABRT with the command {{command|su -c 'service abrtd restart'}}
 
 
# 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
# Click on the Report button in popup bubble applet 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 '''Report'''
+
# Select the entry matching the recently crashed application, click '''Open'''
# Click on Bugzilla button
+
# Go thru the process, select '''Retrace Server''' as a analyzer and choose Bugzilla as a reporting plug-in
# Check the box marked "I checked backtrace and removed sensitive data (password, etc)" - after checking, of course
+
# When asked, enter your Bugzilla account information
# At the report window, click '''Send report'''
+
# Send the crash report to Bugzilla
# 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
 
 
|results=
 
|results=
# A popup message should appear, with information 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.
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 15:08, 15 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, select Retrace Server as a analyzer and choose Bugzilla as a reporting plug-in
  8. When asked, enter your Bugzilla account information
  9. Send the crash report to Bugzilla

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.