From Fedora Project Wiki

(Add to Category:Package_report_test_cases)
(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]].  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 bugzilla. A valid bugzilla username and password is required for this test, please refer to [[BugsAndFeatureRequests]].
|setup=Download, or [[How_to_build_a_Rawhide_ISO_image_for_testing|create]], boot media needed to boot and test the Fedora installer
|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 one of the methods 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.
#* To trigger a failure which is already recorded in bugzilla, add the following boot parameter <pre>updates=http://jlaska.fedorapeople.org/updates/traceback.img</pre>
# After a few initial steps (language/keymap choice, network activation) you should be presented with a failure dialog. Select '''Save'''
#* To trigger a new failure and have the installer create a new bugzilla, add the following boot parameters <pre>updates=http://jlaska.fedorapeople.org/updates/traceback.img randomize_tb</pre>
# 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 [http://fedoraproject.org/wiki/Anaconda/Stage stage2] of the installer, you will be presented with a failure dialog. Select '''Save'''
# On the following dialog, choose '''bugzilla.redhat.com''' from the destination list.
# On the following dialog, choose '''bugzilla.redhat.com''' from the destination list.
# Enter a valid bugzilla ''username'' and ''password'', and select '''OK'''.
# Enter a valid bugzilla ''username'' and ''password'', and select '''OK'''.

Revision as of 09:40, 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. A valid bugzilla username and password is required for this test, please refer to BugsAndFeatureRequests.

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 bugzilla.redhat.com from the destination list.
  4. Enter a valid bugzilla username and password, and select OK.

Expected Results

  1. The installer presents a failure dialog and offers an option to save the failure report.
  2. The Bug description is pre-populated with information about the traceback.
  3. 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
  4. Details of the failure are attached to the bug report
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Anaconda_save_traceback_to_bugzilla&oldid=272504"