From Fedora Project Wiki

m (Moved to different category)
No edit summary
 
(11 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/CrashCatcher|Crash Catcher]] feature.
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature.
|actions=
|actions=
# Check that the ''crash-catcher'' and ''cc-applet'' processes are both running
# Check that the ''abrtd'' 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 some running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package.
# Kill at least two different running processes.
{{admon/warning|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.}}
{{admon/tip|Good candidates|If you don't have your favorite package to crash here are few examples:
* bash
* sleep
* top }}
|results=
|results=
# The ''cc-applet'' system tray icon should start to flash
# The notification stating "We're sorry it looks like a problem occurred. If you'd like to help ..." should appear
# Clicking on the icon should give you an option to open a GUI
# Clicking the "Report" button should open the ABRT GUI (no need to report)
# The GUI should let you select and report the crash
}}
}}
[[Category:ABRT_Test_Cases]]

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.
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.
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)



Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT&oldid=409555"