From Fedora Project Wiki

No edit summary
No edit summary
 
(29 intermediate revisions by 11 users not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Bugzilla'' plugin.
|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 the [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 'dnf install libreport-plugin-bugzilla'}}
# Edit ''/etc/abrt/abrt.conf'' to '''enable''' and '''activate''' the ''Bugzilla'' plugin. A sample config is noted below
# Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running
#: <pre>
# Generate a random unique crash with: {{command|will_abort --random}}.
#: # common abrt settings
# Start gnome-abrt (either from cmdline or from application menu)
#: [ Common ]
# Select the entry matching the recently crashed application, then click '''Report''' button.
#: # enabled plugins
# Write "ABRT testing, please disregard" in problem description
#: # there has to be exactly one database plugin
# Go through the wizard, review the data and start reporting.
#: EnabledPlugins = Bugzilla, Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Python
# Notification should appear prompting you to provide your Bugzilla credentials
#: # reporters association with analyzers
# 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}}).
#: [ AnalyzerActionsAndReporters ]
 
#: CCpp = Mailx, Bugzilla, Logger
#: Python = Mailx, Bugzilla, Logger
#: </pre>
# Edit ''~/.abrt/Bugzilla.conf'' and make sure the configuration is valid. Insert your bugzilla username and password
#: <pre>
#: BugzillaURL = https://bugzilla.redhat.com/xmlrpc.cgi
#: NoSSLVerify = yes
#: #enter your login here
#: Login =
#: #enter your password here
#: Password =
#: </pre>
# Optionally, you may set up the username and password using ''abrt-gui''.  Launch ''abrt-gui'' and select ''Edit -> Preferences -> Enable Bugzilla -> Configure plugin''.  Once complete, confirm that ''~/.abrt/Bugzilla.conf'' lists the information supplied.
# Restart ABRT: <pre># service abrt restart</pre>
# Ensure that the ''abrt'' and ''abrt-applet'' processes are both running
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package
# Click on the panel applet to start ''abrt-gui''
# Select the entry matching the recently crashed application, click '''Report'''
# At the report window, click '''Send'''
|results=
|results=
# A popup message should say: "Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=NNNNNN"
# Log message should appear, with information about the crash and a link to the reported bug
# A bug entry should be filled in the Bugzilla, the entry should be assigned to the package you crashed.
# 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).
# Now it might be a good idea to close the entry in Bugzilla since this "crash" was intended failured and produced by us, so, package maintained won't get upset by a bunch of bogus crashes.
 
After completing this test case, please '''close the bug as NOTABUG'''.
}}
}}
[[Category:ABRT_Test_Cases]]
[[Category:Package_abrt_test_cases]]

Latest revision as of 11:35, 10 April 2015

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 'dnf install libreport-plugin-bugzilla'
  2. Ensure that the abrtd and abrt-applet processes are both running
  3. Generate a random unique crash with: will_abort --random.
  4. Start gnome-abrt (either from cmdline or from application menu)
  5. Select the entry matching the recently crashed application, then click Report button.
  6. Write "ABRT testing, please disregard" in problem description
  7. Go through the wizard, review the data and start reporting.
  8. Notification should appear prompting you to provide your Bugzilla credentials
  9. 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=409562"