From Fedora Project Wiki

(minor cleanups)
No edit summary
(6 intermediate revisions by 3 users not shown)
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=
# 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
# Ensure you have the plugin installed with the command {{command|su -c 'yum install libreport-plugin-bugzilla'}}
# 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
# Click on the '''Open ABRT''' button in pop-up notification to start ''abrt-gui''
# Start gnome-abrt (either from cmdline or from application menu)
# Select the entry matching the recently crashed application, click '''Open'''
# Select the entry matching the recently crashed application, then click '''Analyze''' button.
# Write "ABRT2 testing, please disregard" in problem description
# Write "ABRT2 testing, please disregard" in problem description
# At reporting step, choose Bugzilla as a reporting event
# At reporting step, choose '''Bugzilla''' as a reporting event
# Use "Configure Events" button in the same window to set up your Bugzilla account information
# Notification should appear prompting you to set up your Bugzilla account information, click Configure Bugzilla and use your Bugzilla credentials.
# 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 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}}).
# 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 notification message should appear, with information about the crash 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'''.
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"