From Fedora Project Wiki
(adjust to match text mode as well) |
(Added text mode instructions.) |
||
| Line 5: | Line 5: | ||
|setup=Download and prepare any Fedora installation medium. | |setup=Download and prepare any Fedora installation medium. | ||
|actions= | |actions= | ||
# Boot the installer by any available means. | # Boot the installer by any available means. | ||
#* To boot the installer in the text mode, hit TAB in the boot menu and add <code>inst.text</code> into the command prompt. This option is not available for the Live images. | |||
# 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). | # 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). | ||
# Check that a file with all the crash details has been created in {{filename|/tmp/anaconda-tb-*}}. | # Check that a file with all the crash details has been created in {{filename|/tmp/anaconda-tb-*}}. | ||
Revision as of 15:31, 16 March 2018
Associated release criterion
This test case is associated with the Basic_Release_Criteria#failure-reporting release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Basic_Release_Criteria#failure-reporting release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
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 and prepare any Fedora installation medium.
How to test
- Boot the installer by any available means.
- To boot the installer in the text mode, hit TAB in the boot menu and add
inst.textinto the command prompt. This option is not available for the Live images.
- To boot the installer in the text mode, hit TAB in the boot menu and add
- 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). - Check that a file with all the crash details has been created in
/tmp/anaconda-tb-*. - Report the exception to Bugzilla using the error prompt.
- If you used the fake exception handling trigger, go to Bugzilla and close the newly reported bug as NOTABUG.
Expected Results
- The installer presents a failure prompt and allows you to report it to Bugzilla.
- Exception traceback is displayed.
- Crash details are saved into
/tmp/anaconda-tb-*. - After reporting to Bugzilla, depending on the traceback you are either informed that a new bug was created, or that an existing bug was found that matches this failure. Either way, a bug number is provided.
- Details of the failure are attached to the bug report.