From Fedora Project Wiki

(rewrite to use correct test case template, drop the additional tests which should be separate test cases)
Line 1: Line 1:
== [Configuration] ==
+
{{QA/Test_Case
 
+
|description=This test case tests that [[Features/ABRT|ABRT]]'s ability to report crashes to Bugzilla works correctly.
* If you don't have an account on the [https://bugzilla.redhat.com bugzilla], [https://bugzilla.redhat.com/createaccount.cgi create] one.
+
|actions=
* Edit <code>/etc/abrt/abrt.conf</code> and list the ''CCpp'' and ''Python'' lines (activate it). For example:
+
# If you don't have an account on [https://bugzilla.redhat.com Bugzilla], [https://bugzilla.redhat.com/createaccount.cgi create] one.
 +
# Edit {{filename|/etc/abrt/abrt.conf}} and ensure the Bugzilla plugin is listed on the ''CCpp'' and ''Python'' lines. For example:
 
<pre>
 
<pre>
 
...
 
...
Line 9: Line 10:
 
...
 
...
 
</pre>
 
</pre>
 
+
# Restart ABRT with the command {{command|su -c service abrtd restart}}
* Edit ''/etc/abrt/plugins/Bugzilla.conf'' and make sure the configuration is valid. Insert your bugzilla username and password. Or you can wait and you will be invoke to set password and login before sending report
+
# Ensure that the ''abrt'' 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
Enabled = yes
+
# Click on the Report button in popup bubble applet to start ''abrt-gui''
# Bugzilla URL
+
# Select the entry matching the recently crashed application, click '''Report'''
BugzillaURL = https://bugzilla.redhat.com/
+
# Click on Bugzilla button
# yes means that ssl certificates will not be checked
+
# Check the box marked "I checked backtrace and removed sensitive data (password, etc)" - after checking, of course
NoSSLVerify = no
+
# At the report window, click '''Send report'''
# your login has to exist, if you don have any, please create one
+
# Enter your Bugzilla account information if prompted for it; if you have not already configured abrt to know your username and password, you should be
Login =
+
|results=
# your password
+
# A popup message should appear, with information and a link to the reported bug
Password =
+
# 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
</pre>
+
}}
 
+
[[Category:ABRT_Test_Cases]]
* 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 ''/etc/abrt/plugins/Bugzilla.conf'' lists the information supplied.
 
* Restart ABRT: <pre>$ service abrt restart</pre>
 
 
 
== [Test 'report'] ==
 
* 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 Report button in popup bubble applet to start ''abrt-gui''
 
* Select the entry matching the recently crashed application, click '''Report'''
 
* Click on Bugzilla button
 
* Check out "I checked backtrace and removed sensitive data(password, etc)". Please do the check. 
 
* At the report window, click '''Send report'''
 
 
 
Results:
 
* A popup message should say:
 
    ''STATUS: NEW(or proper status if you hit already reported bug)''
 
    ''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.
 
* Store link to bug
 
 
 
== [Test 'duplicate jump'] ==
 
* Open browser with reported bug(click on link or copy&paste it into your favorite browser)
 
* Modified Status whiteboard(for example erase some letters or add some)
 
* File a new bug(does not matter if is same application), but be sure that new bug is not already reported and close it as CLOSE DUPLICATE where duplicate id is your modified bug
 
* Try to report again bug
 
 
 
Result:
 
* A progress message should say:
 
''Bugzilla(<id>): Jump to bug <id>''
 
* A popup message should say:
 
    ''STATUS: proper status''
 
    ''Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=NNNNNN'' <-- link should be your modified bug.
 
 
 
== [Test 'limit jump only 5x'] ==
 
* Chain 6 bugs as you did in [Test 2]
 
* Run test
 
Result:
 
* A progress message should say:
 
''Bugzilla(<id>): Jump to bug <id>''
 
 
 
A popup message should say:
 
''Bugzilla couldn't find parent of bug(<id>)''
 

Revision as of 23:14, 31 March 2010

Description

This test case tests that ABRT's ability to report crashes to Bugzilla works correctly.


How to test

  1. If you don't have an account on Bugzilla, create one.
  2. Edit /etc/abrt/abrt.conf and ensure the Bugzilla plugin is listed on the CCpp and Python lines. For example:
...
CCpp = Bugzilla
Python = Bugzilla
...
  1. Restart ABRT with the command su -c service abrtd restart
  2. Ensure that the abrt 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. Click on the Report button in popup bubble applet to start abrt-gui
  5. Select the entry matching the recently crashed application, click Report
  6. Click on Bugzilla button
  7. Check the box marked "I checked backtrace and removed sensitive data (password, etc)" - after checking, of course
  8. At the report window, click Send report
  9. Enter your Bugzilla account information if prompted for it; if you have not already configured abrt to know your username and password, you should be

Expected Results

  1. A popup message should appear, with information 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