From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Bugzilla'' plugin. | |description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Bugzilla'' plugin. | ||
|actions= | |actions= | ||
# | # If you don't have an account on the [https://bugzilla.redhat.com bugzilla], [https://bugzilla.redhat.com/createaccount.cgi create] one. | ||
# Edit ''/etc/abrt/abrt.conf'' to '''enable''' and '''activate''' the ''Bugzilla'' plugin. A sample config is noted below | # Edit ''/etc/abrt/abrt.conf'' to '''enable''' and '''activate''' the ''Bugzilla'' plugin. A sample config is noted below | ||
<pre> | <pre> | ||
Line 9: | Line 9: | ||
# enabled plugins | # enabled plugins | ||
# there has to be exactly one database plugin | # there has to be exactly one database plugin | ||
EnabledPlugins = Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter | EnabledPlugins = Bugzilla, Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Python | ||
# reporters association with analyzers | # reporters association with analyzers | ||
[ AnalyzerActionsAndReporters ] | [ AnalyzerActionsAndReporters ] | ||
Line 15: | Line 15: | ||
Python = Mailx, Bugzilla, Logger | Python = Mailx, Bugzilla, Logger | ||
</pre> | </pre> | ||
# Edit ''~/.abrt/Bugzilla.conf'' and make sure the configuration is valid. Insert your username and password | # Edit ''~/.abrt/Bugzilla.conf'' and make sure the configuration is valid. Insert your bugzilla username and password | ||
<pre> | <pre> | ||
BugzillaURL = https://bugzilla.redhat.com/xmlrpc.cgi | BugzillaURL = https://bugzilla.redhat.com/xmlrpc.cgi | ||
Line 24: | Line 24: | ||
Password = | Password = | ||
</pre> | </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. | |||
Restart ABRT: <pre># service abrt restart</pre> | Restart ABRT: <pre># service abrt restart</pre> | ||
Line 31: | Line 33: | ||
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package | # 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'' | # Click on the panel applet to start ''abrt-gui'' | ||
# Select the entry matching the recently crashed application, select | # Select the entry matching the recently crashed application, select ''Generate'' | ||
# At the report window, click '' | # At the report window, click ''Send'' | ||
|results= | |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:ABRT_Test_Cases]] |
Revision as of 10:37, 19 August 2009
Description
This test case tests the functionality of the ABRT feature using the Bugzilla plugin.
How to test
- If you don't have an account on the bugzilla, create one.
- 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 = Bugzilla, Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Python # reporters association with analyzers [ AnalyzerActionsAndReporters ] CCpp = Mailx, Bugzilla, Logger Python = Mailx, Bugzilla, Logger
- Edit ~/.abrt/Bugzilla.conf and make sure the configuration is valid. Insert your bugzilla username and password
BugzillaURL = https://bugzilla.redhat.com/xmlrpc.cgi NoSSLVerify = yes #enter your login here Login = #enter your password here Password =
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.
Restart ABRT:
# service abrt restart
And final steps are:
- Ensure that the abrt and abrt-applet processes are both running
- Kill a running process: kill -SIGSEGV (pid). 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
Expected 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.