From Fedora Project Wiki
(use 'traceback' option) |
(clarify using a Live image) |
||
(2 intermediate revisions by the same user not shown) | |||
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 | |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 | # Boot the installer by any available means | ||
#* If you're running from the Live image, you need to start anaconda from a terminal by running the command <pre>$ liveinst</pre> instead of just clicking on an icon. | |||
# Execute some commands in debug mode | # 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 prompt | |||
#* On a Live image, you need to manually switch back to the terminal which you ran <code>liveinst</code> from | |||
# Execute some commands in the debug mode, e.g.: <pre>(Pdb) locals()</pre> | |||
# Use ''continue'' to return back to the failure prompt: <pre>(Pdb) continue</pre> | |||
#* On a Live image, you need to switch back to anaconda manually | |||
|results= | |results= | ||
# The installer presents a failure | # The installer presents a failure prompt and offers an option to enter the debug mode | ||
# | # 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 prompt and it becomes responsive again (you can press its buttons) | |||
}} | }} | ||
[[Category:Recovery Test Cases]] | [[Category:Recovery Test Cases]] |
Latest revision as of 09:08, 3 December 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
- Boot the installer by any available means
- If you're running from the Live image, you need to start anaconda from a terminal by running the command
$ liveinst
instead of just clicking on an icon.
- If you're running from the Live image, you need to start anaconda from a terminal by running the command
- 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). - Enter a debug mode using the failure prompt
- On a Live image, you need to manually switch back to the terminal which you ran
liveinst
from
- On a Live image, you need to manually switch back to the terminal which you ran
- Execute some commands in the debug mode, e.g.:
(Pdb) locals()
- Use continue to return back to the failure prompt:
(Pdb) continue
- On a Live image, you need to switch back to anaconda manually
Expected Results
- The installer presents a failure prompt and offers an option to enter the debug mode
- You are switched to a debug shell
- Commands are executed successfully in debug shell
- continue returns you back to the failure prompt and it becomes responsive again (you can press its buttons)