From Fedora Project Wiki

(add obsolete category)
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{admon/important|This test case is obsolete|Because of [http://lists.fedoraproject.org/pipermail/test/2012-September/110231.html changes in libreport in Fedora 18] this test case is no longer valid.}}
 +
 
{{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/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.
 +
|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/traceback.img updates.img] using this method below.
+
# Boot the installer by any available means (CD, DVD, boot.iso or PXE). Add a <code>traceback</code> keyword to the kernel boot line.
<pre>updates=http://jlaska.fedorapeople.org/traceback.img</pre>
+
# After a few initial steps (language/keymap choice, network activation) you should be presented with a failure dialog.  Select '''Save'''
# If you also wish to test
+
# On the following dialog, choose '''Report uploader''' as the reporter and provide valid '''scp''' or '''ftp''' URL where to save the report, i.e. <code>scp://login:password@host/path</code> or <code>ftp://login:password@host/path</code>.
# 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 '''Remote server''' from the destination list.
 
# Enter a valid ''User name'',''password'',''Host:port'',''Destination file'', 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 ''Dump Written'' pops up to show the error files has been successfully written
+
# The reporter informs you that the error file 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]]
 +
[[Category:Obsolete Test Cases]]

Latest revision as of 17:06, 21 September 2012

Important.png
This test case is obsolete
Because of changes in libreport in Fedora 18 this test case is no longer valid.


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.

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). Add a traceback keyword to the kernel boot line.
  2. After a few initial steps (language/keymap choice, network activation) you should be presented with a failure dialog. Select Save
  3. On the following dialog, choose Report uploader as the reporter and provide valid scp or ftp URL where to save the report, i.e. scp://login:password@host/path or ftp://login:password@host/path.

Expected Results

  1. The installer presents a failure dialog and offers an option to save the failure report.
  2. The reporter informs you that the error file has been successfully written
  3. Login the remote server, and verify that the file was copied correctly