From Fedora Project Wiki

No edit summary
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 2: Line 2:
|description=This test case checks whether ABRT removes security information after a user reviewed the data which will be filled in the Bugzilla bug report.
|description=This test case checks whether ABRT removes security information after a user reviewed the data which will be filled in the Bugzilla bug report.
|actions=
|actions=
# Generate crash (e.g. run "$ will_abort --random" or kill some process with SIGSEGV "$ sleep 100 &" "$ kill -SEGV %1")
# Generate crash (e.g. run "$ will_abort --random" or kill some process with SIGSEGV signal "$ sleep 100 &" "$ kill -SEGV %1")
# Report the crash with gnome-abrt to Bugzilla
# Report the crash with gnome-abrt to Partner Bugzilla (https://partner-bugzilla.redhat.com/ - testing instance of bugzilla.redhat.com)
# In a review part of the reporting process change content of all possible dump dir elements (e.g. backtrace, cmdline, executable, environ etc.)
## Temporary change url to Bugzilla
# After the Bugzilla report is created, check that all the changes you've made are reflected in the Bugzilla report.
### click on '''Problem Reporting''' menu and choose '''Preferences''' '''(1.)'''
### select '''Events''' list '''(2.)'''
### select '''Bugzilla Report to Bugzilla bug tracker''' item and click '''Configure''' button '''(3.)'''
### in list '''Advanced (4.)''' set '''Bugzilla URL (5.)''' to https://partner-bugzilla.redhat.com/ [[File:change_bugzilla_url.png]]
## Select created crash and click '''Report''' button situated right top in the main gnome-abrt window
## Select '''Reported to Fedora''' workflow
## Generate stack trace (locally or remote using retrace server)
## Write some description
## Now there is important part of the test - data review part
### change a text content of all possible dump directory elements (e.g. add a sentence to the hostname file etc.) [[File:Review.png]]
### Click '''Forward''' button
### There is another review part, so just click '''I reviewed the data and agree with submitting it''' check button and click '''Forward''' button
## Enter your partner Bugzilla credential (same as for Bugzilla)
## New partner Bugzilla bug report should be created
# Visit the new created partner bugzilla bug report
# Check whether all changes you've made in review part are reflected in the bug report
 
|results=
# All the content changes you've made during reporting are reflected in the Bugzilla report.
}}
}}
[[Category:Package_abrt_test_cases]]
[[Category:Package_abrt_test_cases]]

Latest revision as of 14:13, 1 December 2015

Description

This test case checks whether ABRT removes security information after a user reviewed the data which will be filled in the Bugzilla bug report.


How to test

  1. Generate crash (e.g. run "$ will_abort --random" or kill some process with SIGSEGV signal "$ sleep 100 &" "$ kill -SEGV %1")
  2. Report the crash with gnome-abrt to Partner Bugzilla (https://partner-bugzilla.redhat.com/ - testing instance of bugzilla.redhat.com)
    1. Temporary change url to Bugzilla
      1. click on Problem Reporting menu and choose Preferences (1.)
      2. select Events list (2.)
      3. select Bugzilla Report to Bugzilla bug tracker item and click Configure button (3.)
      4. in list Advanced (4.) set Bugzilla URL (5.) to https://partner-bugzilla.redhat.com/
    2. Select created crash and click Report button situated right top in the main gnome-abrt window
    3. Select Reported to Fedora workflow
    4. Generate stack trace (locally or remote using retrace server)
    5. Write some description
    6. Now there is important part of the test - data review part
      1. change a text content of all possible dump directory elements (e.g. add a sentence to the hostname file etc.)
      2. Click Forward button
      3. There is another review part, so just click I reviewed the data and agree with submitting it check button and click Forward button
    7. Enter your partner Bugzilla credential (same as for Bugzilla)
    8. New partner Bugzilla bug report should be created
  3. Visit the new created partner bugzilla bug report
  4. Check whether all changes you've made in review part are reflected in the bug report

Expected Results

  1. All the content changes you've made during reporting are reflected in the Bugzilla report.