From Fedora Project Wiki

(Created page with '{{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 remote system....')
 
Line 2: Line 2:
 
|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 remote system.  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 remote system.  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, you must direct the installer towards an [http://jlaska.fedorapeople.org/traceback.img updates.img] using this methods below.
+
# Boot the installer by any available means (CD, DVD, boot.iso or PXE).  When booting, you must direct the installer towards an [http://jlaska.fedorapeople.org/traceback.img updates.img] using this method below.
 
<pre>updates=http://jlaska.fedorapeople.org/traceback.img</pre>
 
<pre>updates=http://jlaska.fedorapeople.org/traceback.img</pre>
 
# If you also wish to test  
 
# If you also wish to test  

Revision as of 10:07, 25 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 remote system. 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

  1. Boot the installer by any available means (CD, DVD, boot.iso or PXE). When booting, you must direct the installer towards an updates.img using this method below.
updates=http://jlaska.fedorapeople.org/traceback.img
  1. If you also wish to test
  2. When prompted, make language and keyboard selections.
  3. Depending on your installation method, you maybe prompted for a remote installation source. Make a selection and continue.
  4. Upon entering stage#2 of the installer, you will be presented with a failure dialog. Select Save
  5. On the Save dialog, choose Remote server from the destination list.
  6. Enter a valid User name,password,Host:port,Destination file, and select OK.

Expected Results

  1. The installer presents a failure dialog and offers an option to save the failure report.
  2. The Dump Written pops up to show the error files has been successfully written
  3. Login the remote server,the file was created