From Fedora Project Wiki
(update to cover default package set for dedicated installer images) |
Ahmadsamir (talk | contribs) (optical disc not disk) |
||
| Line 8: | Line 8: | ||
|description=This test case is to test that boot and default repository installation work on a given install-capable Fedora medium, assuming working hardware and no showstopper issues in areas covered by other test cases. Non-install-capable media are covered by other test cases. | |description=This test case is to test that boot and default repository installation work on a given install-capable Fedora medium, assuming working hardware and no showstopper issues in areas covered by other test cases. Non-install-capable media are covered by other test cases. | ||
|setup= | |setup= | ||
# Prepare your test system for booting and installing from an install-capable Fedora image. This may involve writing the image to a USB key, or burning it to an optical | # Prepare your test system for booting and installing from an install-capable Fedora image. This may involve writing the image to a USB key, or burning it to an optical disc. If the image you are installing from is a network install image, ensure the system has a working network connection. | ||
|actions= | |actions= | ||
# Boot the system from the prepared optical or USB media. | # Boot the system from the prepared optical or USB media. | ||
Revision as of 08:41, 29 April 2016
Associated release criterion
This test case is associated with the Basic_Release_Criteria#initialization-requirements 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#initialization-requirements 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.
Associated release criterion
This test case is associated with the Basic_Release_Criteria#expected-image-boot-behavior 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#expected-image-boot-behavior 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.
Associated release criterion
This test case is associated with the Basic_Release_Criteria#dvd-package-source 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#dvd-package-source 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.
Associated release criterion
This test case is associated with the Basic_Release_Criteria#package-sets 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#package-sets 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.
Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#default-package-set 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 Fedora_42_Beta_Release_Criteria#default-package-set 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 to test that boot and default repository installation work on a given install-capable Fedora medium, assuming working hardware and no showstopper issues in areas covered by other test cases. Non-install-capable media are covered by other test cases.
Setup
- Prepare your test system for booting and installing from an install-capable Fedora image. This may involve writing the image to a USB key, or burning it to an optical disc. If the image you are installing from is a network install image, ensure the system has a working network connection.
How to test
- Boot the system from the prepared optical or USB media.
- In the boot menu select the appropriate option to boot the image.
- Once booted, run the installer (if necessary) and complete an installation using default settings where possible, and making the most simple and obvious choices where any choice is required (if the network connection requires configuration, configure it). In particular, do not adjust the default repository configuration in any way. Ideally, use an empty disk or a disk that can be entirely wiped, to reduce the likelihood of storage issues interfering with the test.
Expected Results
- A boot menu must be displayed for users to select install options. Navigating the menu and selecting entries must work. If no option is selected, the installer (or live environment) must load after a reasonable timeout.
- If the image under test is a dedicated installer image, the default package set must be the intended default for that image.
- An installation using the default install repository for the image under test must reach the package installation stage successfully (failures once package installation begins are likely out of scope for this test case).
- If the image under test is intended to act as a package source, it must be the default repository and installation must in fact use the media as the package source.