From Fedora Project Wiki
m (initial draft) |
m (Updated content) |
||
| Line 1: | Line 1: | ||
{{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]]. | |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]]. | ||
|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 (CD, DVD, boot.iso or PXE). When booting, add the following boot parameter <pre>updates=http://jlaska.fedorapeople.org/traceback.img</pre> | ||
| Line 7: | Line 7: | ||
# Upon entering stage#2 of the installer, you will be presented with a failure dialog. Select '''Save''' | # Upon entering stage#2 of the installer, you will be presented with a failure dialog. Select '''Save''' | ||
# On the Save dialog, choose '''Bugzilla''' from the destination list. | # On the Save dialog, choose '''Bugzilla''' from the destination list. | ||
# Enter a valid bugzilla username and password, and select '''OK'''. | # Enter a valid bugzilla ''username'' and ''password'', and select '''OK'''. | ||
|results= | |results= | ||
# The installer presents a failure dialog and offers an option to save the failure report. | # The installer presents a failure dialog and offers an option to save the failure report. | ||
# | # The ''Bug description'' is pre-populated with information about the traceback. | ||
# 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 | |||
# Details of the failure are attached to the bug report | |||
}} | }} | ||
Revision as of 16:52, 4 November 2009
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 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.
How to test
- Boot the installer by any available means (CD, DVD, boot.iso or PXE). When booting, add the following boot parameter
updates=http://jlaska.fedorapeople.org/traceback.img
- When prompted, make language and keyboard selections.
- Depending on your installation method, you maybe prompted for a remote installation source. Make a selection and continue.
- Upon entering stage#2 of the installer, you will be presented with a failure dialog. Select Save
- On the Save dialog, choose Bugzilla from the destination list.
- Enter a valid bugzilla username and password, and select OK.
Expected Results
- The installer presents a failure dialog and offers an option to save the failure report.
- The Bug description is pre-populated with information about the traceback.
- 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
- Details of the failure are attached to the bug report