From Fedora Project Wiki

 
(19 intermediate revisions by 8 users not shown)
Line 1: Line 1:
== [Configuration] ==
+
{{QA/Test_Case
 +
|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=
 +
# Ensure you have the plugin installed with the command {{command|su -c 'dnf install libreport-plugin-bugzilla'}}
 +
# Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running
 +
# Generate a random unique crash with: {{command|will_abort --random}}.
 +
# Start gnome-abrt (either from cmdline or from application menu)
 +
# Select the entry matching the recently crashed application, then click '''Report''' button.
 +
# Write "ABRT testing, please disregard" in problem description
 +
# Go through the wizard, review the data and start reporting.
 +
# Notification should appear prompting you to provide your Bugzilla credentials
 +
# 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}}).
  
* If you don't have an account on the [https://bugzilla.redhat.com bugzilla], [https://bugzilla.redhat.com/createaccount.cgi create] one.
+
|results=
* Edit <code>/etc/abrt/abrt.conf</code> and list the ''CCpp'' and ''Python'' lines (activate it). For example:
+
# Log message should appear, with information about the crash and a link to the reported bug
<pre>
+
# 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).
...
 
CCpp = Bugzilla
 
Python = Bugzilla
 
...
 
</pre>
 
  
* 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
+
After completing this test case, please '''close the bug as NOTABUG'''.
<pre>
+
}}
Enabled = yes
+
[[Category:Package_abrt_test_cases]]
# Bugzilla URL
 
BugzillaURL = https://bugzilla.redhat.com/
 
# yes means that ssl certificates will not be checked
 
NoSSLVerify = no
 
# your login has to exist, if you don have any, please create one
 
Login =
 
# your password
 
Password =
 
</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 ''/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>)''
 

Latest revision as of 11:35, 10 April 2015

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 'dnf install libreport-plugin-bugzilla'
  2. Ensure that the abrtd and abrt-applet processes are both running
  3. Generate a random unique crash with: will_abort --random.
  4. Start gnome-abrt (either from cmdline or from application menu)
  5. Select the entry matching the recently crashed application, then click Report button.
  6. Write "ABRT testing, please disregard" in problem description
  7. Go through the wizard, review the data and start reporting.
  8. Notification should appear prompting you to provide your Bugzilla credentials
  9. 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.