From Fedora Project Wiki

Revision as of 14:53, 18 August 2009 by Dnovotny (talk | contribs) (Created page with '{{QA/Test_Case |description=This test case tests the functionality of the ABRT feature using the ''Bugzilla'' plugin. |actions= # if you don't have an account o...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Description

This test case tests the functionality of the ABRT feature using the Bugzilla plugin.


How to test

  1. if you don't have an account on the bugzilla (https://bugzilla.redhat.com), create one
  2. Edit /etc/abrt/abrt.conf to enable and activate the Bugzilla plugin. A sample config is noted below
# common abrt settings
[ Common ]
# enabled plugins
# there has to be exactly one database plugin
EnabledPlugins = Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python
# reporters association with analyzers
[ AnalyzerActionsAndReporters ]
CCpp = Mailx, Bugzilla, Logger
Python = Mailx, Bugzilla, Logger
  1. Edit ~/.abrt/Bugzilla.conf and make sure the configuration is valid. Insert your username and password
BugzillaURL = https://bugzilla.redhat.com/xmlrpc.cgi
NoSSLVerify = yes
#enter your login here
Login =
#enter your password here
Password =

Restart ABRT: 

# service abrt restart

And final steps are:

  1. Ensure that the abrt and abrt-applet processes are both running
  2. Kill a running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  3. Click on the panel applet to start abrt-gui
  4. Select the entry matching the recently crashed application, select Generate
  5. At the report window, click Apply

Expected Results

  1. a bug entry should be filled in the Bugzilla, under the package you crashed
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_Bugzilla_plugin&oldid=119480"