From Fedora Project Wiki

(Use new traceback URL)
(use 'traceback' option)
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/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 bugzilla.
 
|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). Add a <code>traceback</code> keyword to the kernel boot line.
# When prompted, make language and keyboard selections.
+
# After a few initial steps (language/keymap choice, network activation) you should be presented with a failure dialog.  Select '''Debug'''
# 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 '''Debug'''
 
 
# Execute some commands in debug mode
 
# Execute some commands in debug mode
 
|results=
 
|results=

Revision as of 09:43, 22 February 2012

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.


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 Debug
  3. Execute some commands in debug mode

Expected Results

  1. The installer presents a failure dialog and offers an option to save the failure report.
  2. Debug shell appears on tty1
  3. Commands are executed successfully in debug shell