From Fedora Project Wiki

(use 'traceback' option)
(new way how to trigger Anaconda's bug reporting dialog, improve instructions)
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.
|description=This test case is intended to introduce a failure, and validate that anaconda is able to enter a debug mode to retrieve detailed crash information
|actions=
|actions=
# Boot the installer by any available means (CD, DVD, boot.iso or PXE). Add a <code>traceback</code> keyword to the kernel boot line.
# Boot the installer by any available means
# After a few initial steps (language/keymap choice, network activation) you should be presented with a failure dialog.  Select '''Debug'''
# If you know how to make Anaconda crash, you can do so. Otherwise use Anaconda's [http://lists.fedoraproject.org/pipermail/test/2012-September/110149.html fake exception handling trigger] - run the following command: <pre>kill -USR1 `cat /var/run/anaconda.pid`</pre> Switch back to the GUI, an error dialog should be displayed.
# Execute some commands in debug mode
# Enter a debug mode using the failure dialog
# Execute some commands in the debug mode, e.g.: <pre>(Pdb) locals()</pre>
# Use ''continue'' to return back to the failure dialog: <pre>(Pdb) continue</pre>
|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 enter the debug mode
# Debug shell appears on tty1
# You are switched to a debug shell
# Commands are executed successfully in debug shell
# Commands are executed successfully in debug shell  
# ''continue'' returns you back to the failure dialog
}}
}}


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

Revision as of 09:41, 20 September 2012

Description

This test case is intended to introduce a failure, and validate that anaconda is able to enter a debug mode to retrieve detailed crash information


How to test

  1. Boot the installer by any available means
  2. If you know how to make Anaconda crash, you can do so. Otherwise use Anaconda's fake exception handling trigger - run the following command:
    kill -USR1 `cat /var/run/anaconda.pid`
    Switch back to the GUI, an error dialog should be displayed.
  3. Enter a debug mode using the failure dialog
  4. Execute some commands in the debug mode, e.g.:
    (Pdb) locals()
  5. Use continue to return back to the failure dialog:
    (Pdb) continue

Expected Results

  1. The installer presents a failure dialog and offers an option to enter the debug mode
  2. You are switched to a debug shell
  3. Commands are executed successfully in debug shell
  4. continue returns you back to the failure dialog