From Fedora Project Wiki
No edit summary |
m (change anchor) |
||
| (20 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{Associated_release_criterion|Beta|package-set-selection}} | |||
{{Associated_release_criterion|Final|minimal-install}} | |||
{{admon/note|Release criteria|The Beta release criterion is violated only if the package set selection mechanism does not work - if, when you select the minimal package set, that set of packages is not actually marked for installation. If that works, but installation of the packages fails, this violates the Final release criterion but not the Beta one.}} | |||
{{Testcase package set|minimal}} | |||
Latest revision as of 02:52, 31 January 2015
Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#package-set-selection 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#package-set-selection 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_Final_Release_Criteria#minimal-install 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_Final_Release_Criteria#minimal-install 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.
Release criteria
The Beta release criterion is violated only if the package set selection mechanism does not work - if, when you select the minimal package set, that set of packages is not actually marked for installation. If that works, but installation of the packages fails, this violates the Final release criterion but not the Beta one.
The Beta release criterion is violated only if the package set selection mechanism does not work - if, when you select the minimal package set, that set of packages is not actually marked for installation. If that works, but installation of the packages fails, this violates the Final release criterion but not the Beta one.
Description
This is to verify that Anaconda can successfully install the minimal package set from the release repository.
Setup
- Prepare a test system with a working, supported storage device of sufficient size for a Fedora install, and a Fedora installation medium that uses the GTK-based installer. Do not use Fedora Workstation live on Fedora 41+, as that uses the webui-based installer.
How to test
- Boot the installer using the generic network install image or a similar method (e.g. PXE boot with the Everything tree used for inst.repo)
- Enter the INSTALLATION SOURCE screen and select the option called Install the default versions provided by the installation source (above) only. If using the generic network install image, the source should be set to Closest mirror. Click Done
- Enter the SOFTWARE SELECTION screen and select the minimal environment
- Proceed with installation, using defaults for all other settings where possible and simple, sensible choices where a choice must be made
- Boot the installed system.
Expected Results
- The installation should complete successfully
- The selected package set should be installed
- The system should boot to the appropriate state for the selected package set.