QA:Testcase ABRT

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(edit the test case to match the current ABRT)
 
(One intermediate revision by one user not shown)
Line 8: Line 8:
 
{{admon/tip|Good candidates|If you don't have your favorite package to crash here are few examples:
 
{{admon/tip|Good candidates|If you don't have your favorite package to crash here are few examples:
 
* bash
 
* bash
* python
 
 
* sleep
 
* sleep
 
* top }}
 
* top }}
 
|results=
 
|results=
# The ''abrt-applet'' system tray icon should emerge with notification stating "Crash in package foo-1.2.3 has been detected"
+
# The notification stating "A problem in in package foo-1.2.3 has been detected" should appear
# Clicking on the notification should open ''abrt-gui''
+
# Clicking the "Report" button should start the reporting wizard (no need to finish the report)
# The GUI should let you select and report the crash (no need to finish the report)
+
# The GUI should let you delete the crash
+
 
}}
 
}}

Latest revision as of 08:33, 22 October 2012

Description

This test case tests the functionality of the ABRT feature.


How to test

  1. Check that the abrtd and abrt-applet processes are both running.
  2. Kill some running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package.
  3. Kill at least two different running processes.
Warning (medium size).png
When using a live image
Please don't kill large applications (e.g. Firefox), because the coredumps and downloaded debuginfo packages take large amount of space and it could exhaust all your available memory.
Idea.png
Good candidates
If you don't have your favorite package to crash here are few examples:
  • bash
  • sleep
  • top

Expected Results

  1. The notification stating "A problem in in package foo-1.2.3 has been detected" should appear
  2. Clicking the "Report" button should start the reporting wizard (no need to finish the report)