From Fedora Project Wiki

(dialog was updated)
(Add to Category:Package_report_test_cases)
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 remote system.  This test case relies on an [http://jlaska.fedorapeople.org/updates/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 remote system.  This test case relies on an [http://jlaska.fedorapeople.org/updates/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]].  
|setup=Download, or [[How_to_build_a_Rawhide_ISO_image_for_testing|create]], boot media needed to boot and test the Fedora installer
|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/updates/traceback.img updates.img] using this method below.<pre>updates=http://jlaska.fedorapeople.org/updates/traceback.img</pre>
# 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/updates/traceback.img updates.img] using this method below.<pre>updates=http://jlaska.fedorapeople.org/updates/traceback.img</pre>
Line 11: Line 12:
# 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 ''Dump Written'' pops up to show the error files has been successfully written
# The ''Dump Written'' pops up to show the error files has been successfully written
# Login the remote server,the file was created
# Login the remote server, and verify that the file was copied correctly
}}
}}


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

Revision as of 14:31, 25 April 2011

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.

Setup

Download, or create, boot media needed to boot and test the Fedora installer

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/updates/traceback.img
  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 stage2 of the installer, you will be presented with a failure dialog. Select Save
  5. On the following dialog, choose either scp or ftp
  6. Enter a valid destination specification and confirm.

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, and verify that the file was copied correctly