From Fedora Project Wiki

m (Fix wiki ordered list)
Line 4: Line 4:
 
# If you don't have an account on the [https://bugzilla.redhat.com bugzilla], [https://bugzilla.redhat.com/createaccount.cgi create] one.
 
# 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>
# common abrt settings
+
#: # common abrt settings
[ Common ]
+
#: [ Common ]
# enabled plugins
+
#: # enabled plugins
# there has to be exactly one database plugin
+
#: # there has to be exactly one database plugin
EnabledPlugins = Bugzilla, Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Python
+
#: EnabledPlugins = Bugzilla, Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Python
# reporters association with analyzers
+
#: # reporters association with analyzers
[ AnalyzerActionsAndReporters ]
+
#: [ AnalyzerActionsAndReporters ]
CCpp = Mailx, Bugzilla, Logger
+
#: CCpp = Mailx, Bugzilla, Logger
Python = Mailx, Bugzilla, Logger
+
#: Python = Mailx, Bugzilla, Logger
</pre>
+
#: </pre>
 
# Edit ''~/.abrt/Bugzilla.conf'' and make sure the configuration is valid. Insert your bugzilla 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
NoSSLVerify = yes
+
#: NoSSLVerify = yes
#enter your login here
+
#: #enter your login here
Login =
+
#: Login =
#enter your password here
+
#: #enter your password here
Password =
+
#: Password =
</pre>
+
#: </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.
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>
 
 
 
And final steps are:
 
 
# Ensure that the ''abrt'' and ''abrt-applet'' processes are both running
 
# 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
 
# 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, click '''Report'''
+
# Select the entry matching the recently crashed application, click ''Report''
# At the report window, click '''Send'''
+
# At the report window, click ''Send''
 
|results=
 
|results=
 
# A popup message should say: "Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=NNNNNN"
 
# A popup message should say: "Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=NNNNNN"
 
# A bug entry should be filled in the Bugzilla, the entry should be assigned to the package you crashed.
 
# 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.
+
# 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.
 
}}
 
}}
 
[[Category:ABRT_Test_Cases]]
 
[[Category:ABRT_Test_Cases]]

Revision as of 13:53, 19 August 2009

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, 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 = Bugzilla, Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Python
    # reporters association with analyzers
    [ AnalyzerActionsAndReporters ]
    CCpp = Mailx, Bugzilla, Logger
    Python = Mailx, Bugzilla, Logger
  3. 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 =
  4. 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.
  5. Restart ABRT:
    # service abrt restart
  6. Ensure that the abrt and abrt-applet processes are both running
  7. Kill a running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  8. Click on the panel applet to start abrt-gui
  9. Select the entry matching the recently crashed application, click Report
  10. At the report window, click Send

Expected Results

  1. A popup message should say: "Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=NNNNNN"
  2. A bug entry should be filled in the Bugzilla, the entry should be assigned to the package you crashed.
  3. 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.