From Fedora Project Wiki

(convert to new category system)
No edit summary
(13 intermediate revisions by 6 users not shown)
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.
# Ensure you have the plugin installed with the command {{command|su -c 'yum install libreport-plugin-bugzilla'}}
# Edit {{filename|/etc/abrt/abrt.conf}} and ensure the Bugzilla plugin is listed on the ''CCpp'' and ''Python'' lines. For example:
#:<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''
# Start gnome-abrt (either from cmdline or from application menu)
# Select the entry matching the recently crashed application, click '''Report'''
# Select the entry matching the recently crashed application, then click '''Analyze''' button.
# Click on Bugzilla button
# Write "ABRT2 testing, please disregard" in problem description
# Check the box marked "I checked backtrace and removed sensitive data (password, etc)" - after checking, of course
# At reporting step, choose '''Bugzilla''' as a reporting event
# At the report window, click '''Send report'''
# Notification should appear prompting you to set up your Bugzilla account information, click Configure Bugzilla and use your Bugzilla credentials.
# 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
# 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 and pasted from the GUI report window, or retrieved from event_log file in problem data directory (e.g. {{filename|/var/tmp/abrt/ccpp-2011-03-04-15:46:26-22496/event_log}}).
 
|results=
|results=
# A popup message should appear, with information and a link to the reported bug
# Log 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 (exception to this is the case when you report duplicate bug - in that case you are added to the CC field of the duplicate and only your comment and package version is posted to the bug report).
 
After completing this test case, please '''close the bug as NOTABUG'''.
}}
}}
[[Category:Package_abrt_test_cases]]
[[Category:Package_abrt_test_cases]]

Revision as of 10:30, 3 May 2013

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. Ensure you have the plugin installed with the command su -c 'yum install libreport-plugin-bugzilla'
  2. Ensure that the abrtd and abrt-applet processes are both running
  3. Kill a running process with the command kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  4. Start gnome-abrt (either from cmdline or from application menu)
  5. Select the entry matching the recently crashed application, then click Analyze button.
  6. Write "ABRT2 testing, please disregard" in problem description
  7. At reporting step, choose Bugzilla as a reporting event
  8. Notification should appear prompting you to set up your Bugzilla account information, click Configure Bugzilla and use your Bugzilla credentials.
  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 and pasted from the GUI report window, or retrieved from event_log file in problem data directory (e.g. /var/tmp/abrt/ccpp-2011-03-04-15:46:26-22496/event_log).

Expected Results

  1. Log 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 (exception to this is the case when you report duplicate bug - in that case you are added to the CC field of the duplicate and only your comment and package version is posted to the bug report).

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

Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_Bugzilla_plugin&oldid=335206"