QA:Testcase ABRT
From FedoraProject
(Difference between revisions)
(livecd warning) |
(edit the test case to match the current ABRT) |
||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 2: | Line 2: | ||
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature. | |description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature. | ||
|actions= | |actions= | ||
| − | # Check that the '' | + | # Check that the ''abrtd'' and ''abrt-applet'' processes are both running. |
# Kill some 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. | ||
| − | {{admon/warning|When using | + | # 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 | + | # The notification stating "A problem in in package foo-1.2.3 has been detected" should appear |
| − | # Clicking | + | # Clicking the "Report" button should start the reporting wizard (no need to finish the report) |
| − | + | ||
}} | }} | ||
| − | |||
Revision as of 08:33, 22 October 2012
Description
This test case tests the functionality of the ABRT feature.
How to test
- Check that the abrtd and abrt-applet processes are both running.
- Kill some running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package.
- 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.
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:
If you don't have your favorite package to crash here are few examples:
- bash
- sleep
- top
Expected Results
- The notification stating "A problem in in package foo-1.2.3 has been detected" should appear
- Clicking the "Report" button should start the reporting wizard (no need to finish the report)
