From Fedora Project Wiki

Line 7: Line 7:
 
will_segfault
 
will_segfault
 
</pre></li>
 
</pre></li>
 +
<li>Configure your Bugzilla credentials - Problem Reporting -> Preferences -> Events -> Bugzilla</li>
 
<li>Notification popup about crash should appear. Click on it or run {{command|gnome-abrt}} manually.</li></ol>
 
<li>Notification popup about crash should appear. Click on it or run {{command|gnome-abrt}} manually.</li></ol>
 
|actions=
 
|actions=
 
<ol>
 
<ol>
<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>Find a new record for the crash in gnome-abrt: <pre>"will-crash"</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>
Line 18: Line 19:
 
--- Running report_uReport ---
 
--- Running report_uReport ---
 
This problem has already been reported.
 
This problem has already been reported.
https://retrace.fedoraproject.org/faf/reports/17932/
+
https://retrace.fedoraproject.org/faf/reports/347291/
https://bugzilla.redhat.com/show_bug.cgi?id=851210
+
https://bugzilla.redhat.com/show_bug.cgi?id=1090572
 +
https://bugzilla.redhat.com/show_bug.cgi?id=1124867
 +
https://bugzilla.redhat.com/show_bug.cgi?id=1143864
 +
https://bugzilla.redhat.com/show_bug.cgi?id=1185157
 +
https://bugzilla.redhat.com/show_bug.cgi?id=1210573
 +
Adding you to CC List of the existing bugzilla bug
 +
Using Bugzilla ID '1210573'
 +
Logging into Bugzilla at https://bugzilla.redhat.com
 +
Logging out
 
</pre>
 
</pre>
 
<li>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.</li>
 
<li>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.</li>
Line 26: Line 35:
 
#'''Reporting should be interrupted because the crash is known.'''
 
#'''Reporting should be interrupted because the crash is known.'''
 
#Crash is not reported to Bugzilla.
 
#Crash is not reported to Bugzilla.
 +
#Your email address was added to CC of Bugzilla bug #1210573
 
}}
 
}}
  
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 06:54, 10 April 2015

Description

Test reporting of known (already reported) crash.

Setup

  1. Prepare a crash:
    yum install will-crash
    will_segfault
    
  2. Configure your Bugzilla credentials - Problem Reporting -> Preferences -> Events -> Bugzilla
  3. 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"
  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/347291/
    https://bugzilla.redhat.com/show_bug.cgi?id=1090572
    https://bugzilla.redhat.com/show_bug.cgi?id=1124867
    https://bugzilla.redhat.com/show_bug.cgi?id=1143864
    https://bugzilla.redhat.com/show_bug.cgi?id=1185157
    https://bugzilla.redhat.com/show_bug.cgi?id=1210573
    Adding you to CC List of the existing bugzilla bug
    Using Bugzilla ID '1210573'
    Logging into Bugzilla at https://bugzilla.redhat.com
    Logging out
    
  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.
  3. Your email address was added to CC of Bugzilla bug #1210573