From Fedora Project Wiki

No edit summary
No edit summary
(30 intermediate revisions by 9 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 'yum 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>
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package
# common abrt settings
# Start gnome-abrt (either from cmdline or from application menu)
[ Common ]
# Select the entry matching the recently crashed application, then click '''Analyze''' button.
# enabled plugins
# Write "ABRT2 testing, please disregard" in problem description
# there has to be exactly one database plugin
# At reporting step, choose '''Bugzilla''' as a reporting event
EnabledPlugins = Bugzilla, Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Python
# Notification should appear prompting you to set up your Bugzilla account information, click Configure Bugzilla and use your Bugzilla credentials.
# reporters association with analyzers
# Proceed to reporting using "Forward"/"Apply" buttons
[ AnalyzerActionsAndReporters ]
# 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}}).
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/password pair via '''abrt-gui -> Edit -> Preferences -> Enable Bugzilla -> Configure plugin''' and check that ''~/.abrt/Bugzilla.conf'' is correct.
|results=
# 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 (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).


Restart ABRT: <pre># service abrt restart</pre>
After completing this test case, please '''close the bug as NOTABUG'''.
 
And final steps are:
# 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, select ''Generate''
# At the report window, click ''Send''
|results=
# A bug entry should be filled in the Bugzilla, the entry should be assigned to the package you crashed.
# Now it might be a good idea to close the entry in Bugzilla WWW since this "crash" was intended and produced by us, so, package maintained won't get upset by a bunch of bogus crashes.
}}
}}
[[Category: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"