From Fedora Project Wiki

(new way how to trigger Anaconda's bug reporting dialog, improve instructions)
(change terminology to match text mode as well)
Line 3: Line 3:
|actions=
|actions=
# Boot the installer by any available means
# Boot the installer by any available means
# 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.
# 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] - switch to a different terminal and run the following command: <pre>kill -USR1 `cat /var/run/anaconda.pid`</pre> Switch back to the installer, an error prompt should be displayed after a few seconds (you might need to click on some UI element to achieve that, or hit ''refresh'' in a text mode).
# Enter a debug mode using the failure dialog
# Enter a debug mode using the failure prompt
# Execute some commands in the debug mode, e.g.: <pre>(Pdb) locals()</pre>
# 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>
# Use ''continue'' to return back to the failure prompt: <pre>(Pdb) continue</pre>
|results=
|results=
# The installer presents a failure dialog and offers an option to enter the debug mode
# The installer presents a failure prompt and offers an option to enter the debug mode
# You are switched to a debug shell
# 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
# ''continue'' returns you back to the failure prompt
}}
}}


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

Revision as of 12:49, 11 November 2014

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 - switch to a different terminal and run the following command:
    kill -USR1 `cat /var/run/anaconda.pid`
    Switch back to the installer, an error prompt should be displayed after a few seconds (you might need to click on some UI element to achieve that, or hit refresh in a text mode).
  3. Enter a debug mode using the failure prompt
  4. Execute some commands in the debug mode, e.g.:
    (Pdb) locals()
  5. Use continue to return back to the failure prompt:
    (Pdb) continue

Expected Results

  1. The installer presents a failure prompt 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 prompt