QA:Testcase ABRT Reporting Known Crash

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(sleep -> will_crash)
 
(One intermediate revision by one user not shown)
Line 10: Line 10:
 
|actions=
 
|actions=
 
<ol>
 
<ol>
<li>Find a new record for sleep: <pre>"coreutils | Process /usr/bin/sleep was killed by signal 11 (SIGSEGV)"</pre></li>
+
<li>Find a new record for the crash in gnome-abrt: <pre>"will-crash | Process /usr/bin/will_segfault was killed by signal 11 (SIGSEGV)"</pre></li>
 
<li>Click on the "Report" button.</li>
 
<li>Click on the "Report" button.</li>
 
<li>Wait until processing is finished.</li>
 
<li>Wait until processing is finished.</li>

Latest revision as of 08:50, 7 May 2013

Contents

Description

Test reporting of known (already reported) crash.

Setup

  1. Prepare a crash:
    yum install will-crash
    will_segfault
    
  2. Notification popup about crash should appear. Click on it or run gnome-abrt manually.

How to test

  1. Find a new record for the crash in gnome-abrt:
    "will-crash | Process /usr/bin/will_segfault was killed by signal 11 (SIGSEGV)"
  2. Click on the "Report" button.
  3. Wait until processing is finished.
  4. Click on "Show log" label.
  5. You should see only the following text:
  6. --- Running report_uReport ---
    This problem has already been reported.
    https://retrace.fedoraproject.org/faf/reports/17932/
    https://bugzilla.redhat.com/show_bug.cgi?id=851210
    
  7. You should not be able to continue with reporting. The "Close" button should be placed in right bottom corner of the reporting window and the button should be the only one visible.

Expected Results

  1. Reporting should be interrupted because the crash is known.
  2. Crash is not reported to Bugzilla.