From Fedora Project Wiki

(edit the test case to match the current ABRT)
No edit summary
 
Line 11: Line 11:
* top }}
* top }}
|results=
|results=
# The notification stating "A problem in in package foo-1.2.3 has been detected" should appear
# The notification stating "We're sorry it looks like a problem occurred. If you'd like to help ..." should appear
# Clicking the "Report" button should start the reporting wizard (no need to finish the report)
# Clicking the "Report" button should open the ABRT GUI (no need to report)
}}
}}

Latest revision as of 10:45, 10 April 2015

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.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 "We're sorry it looks like a problem occurred. If you'd like to help ..." should appear
  2. Clicking the "Report" button should open the ABRT GUI (no need to report)