From Fedora Project Wiki

m (Add to category)
(kill as root)
 
(16 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Template:Associated_release_criterion|Alpha|failure-reporting}}
{{QA/Test_Case
{{QA/Test_Case
|description=This test case is intended to introduce a failure, and validate anaconda is able to properly handle the failure and report the issue to bugzilla. This test case relies on an [http://jlaska.fedorapeople.org/traceback.img updates.img] that will intentionally cause the installation to fail in a manner that is non-destructive to your existing system.  For more information in using an updates.img, see [[Anaconda/Updates]].  A valid bugzilla username and password is required for this test, please refer to [[BugsAndFeatureRequests]].
|description=This test case is intended to introduce a failure, and validate anaconda is able to properly handle the failure and report the issue to bugzilla. A valid bugzilla username and password is required for this test, please refer to [[BugsAndFeatureRequests]].
|setup=Download and prepare any Fedora installation medium.
|actions=
|actions=
# Boot the installer by any available means (CD, DVD, boot.iso or PXE).  When booting, add the following boot parameter <pre>updates=http://jlaska.fedorapeople.org/traceback.img</pre>
# Boot the installer by any available means.
# When prompted, make language and keyboard selections.
#* To boot the installer in the text mode, hit TAB in the boot menu and add <code>inst.text</code> into the command prompt. This option is not available for the Live images.
# Depending on your installation method, you maybe prompted for a remote installation source.  Make a selection and continue.
# If you know how to make Anaconda crash, you can do so. Otherwise use Anaconda's [http://lists.fedoraproject.org/pipermail/test/2012-September/110149.html fake exception handling trigger] - switch to a different terminal and run the following command as root: <pre>kill -USR1 `cat /var/run/anaconda.pid`</pre> Switch back to the installer, an error prompt should be displayed after a few seconds (you might need to click on some UI element to achieve that, or hit ''refresh'' in a text mode).
# Upon entering stage#2 of the installer, you will be presented with a failure dialog. Select '''Save'''
# Check that a file with all the crash details has been created in {{filename|/tmp/anaconda-tb-*}}.
# On the Save dialog, choose '''Bugzilla''' from the destination list.
# Report the exception to Bugzilla using the error prompt.
# Enter a valid bugzilla ''username'' and ''password'', and select '''OK'''.
# If you used the fake exception handling trigger, go to Bugzilla and close the newly reported bug as NOTABUG.
|results=
|results=
# The installer presents a failure dialog and offers an option to save the failure report.
# The installer presents a failure prompt and allows you to report it to Bugzilla.
# The ''Bug description'' is pre-populated with information about the traceback.
# Exception traceback is displayed.
# Depending on the traceback, you are informed that a new bug was created, or that an existing bug was found that matches this failure. Either way, a bug# is provided
# Crash details are saved into {{filename|/tmp/anaconda-tb-*}}.
# Details of the failure are attached to the bug report
# After reporting to Bugzilla, depending on the traceback you are either informed that a new bug was created, or that an existing bug was found that matches this failure. Either way, a bug number is provided.
# Details of the failure are attached to the bug report.
}}
}}


[[Category:Recovery Test Cases]]
[[Category:Recovery Test Cases]]
[[Category:Package_report_test_cases]]

Latest revision as of 10:58, 20 October 2020

Associated release criterion
This test case is associated with the Basic_Release_Criteria#failure-reporting release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

This test case is intended to introduce a failure, and validate anaconda is able to properly handle the failure and report the issue to bugzilla. A valid bugzilla username and password is required for this test, please refer to BugsAndFeatureRequests.

Setup

Download and prepare any Fedora installation medium.

How to test

  1. Boot the installer by any available means.
    • To boot the installer in the text mode, hit TAB in the boot menu and add inst.text into the command prompt. This option is not available for the Live images.
  2. If you know how to make Anaconda crash, you can do so. Otherwise use Anaconda's fake exception handling trigger - switch to a different terminal and run the following command as root: 
    kill -USR1 `cat /var/run/anaconda.pid`
    Switch back to the installer, an error prompt should be displayed after a few seconds (you might need to click on some UI element to achieve that, or hit refresh in a text mode).
  3. Check that a file with all the crash details has been created in /tmp/anaconda-tb-*.
  4. Report the exception to Bugzilla using the error prompt.
  5. If you used the fake exception handling trigger, go to Bugzilla and close the newly reported bug as NOTABUG.

Expected Results

  1. The installer presents a failure prompt and allows you to report it to Bugzilla.
  2. Exception traceback is displayed.
  3. Crash details are saved into /tmp/anaconda-tb-*.
  4. After reporting to Bugzilla, depending on the traceback you are either informed that a new bug was created, or that an existing bug was found that matches this failure. Either way, a bug number is provided.
  5. Details of the failure are attached to the bug report.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Anaconda_save_traceback_to_bugzilla&oldid=591445"