Latest revision as of 18:53, 28 October 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.

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.

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.

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.

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.

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.
- If testing in a virtual machine, attach the image to the virtual machine as a CD or DVD.
- If testing optical media on a real machine, burn the image to a CD or DVD, insert it into the system's optical drive, and ensure the system is configured to boot from the optical drive.
- If testing USB media on a real machine, prepare the USB stick according to the official instructions, using the most prominently-recommended method (currently Fedora Media Writer), and ensure the system is configured to boot from the USB medium.
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 install medium.
In the boot menu select the appropriate option to boot the image.
Once booted, run the installer (if necessary) and complete an installation using the default repository configuration.
- If the network connection requires configuration, configure it.
- Do not adjust the default repository configuration in any way.
- In order to improve the efficiency of release validation testing, it's OK to change any other installation settings (disk layout, language, and so on) so the test run simultaneously covers this test case and some other test case. Any successful install attempt using the media under test and the default repository configuration can be considered a pass for this test. A fail should only be reported if any of the expected results below does not transpire.

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.
- Failures related to some particular installation configuration, pre-existing disk content or system hardware or configuration are also likely out of scope for this test case (but may be a violation of one of the other release validation test cases). If any install attempt using the medium under test and the default repository configuration works, and the other conditions listed here are met, this test should be considered to have passed.
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.

@@ Line 1: / Line 1: @@
+{{Template:Associated_release_criterion|Alpha|initialization-requirements}}
+{{Template:Associated_release_criterion|Alpha|expected-image-boot-behavior}}
+{{Template:Associated_release_criterion|Alpha|dvd-package-source}}
+{{Template:Associated_release_criterion|Alpha|package-sets}}
+{{Template:Associated_release_criterion|Beta|default-package-set}}
 {{QA/Test_Case
 |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 disk. If the image you are installing from is a network install image, ensure the system has a working network connection.
+# Prepare your test system for booting and installing from an install-capable Fedora image.
+#* If testing in a virtual machine, attach the image to the virtual machine as a CD or DVD.
+#* If testing optical media on a real machine, [http://docs.fedoraproject.org/readme-burning-isos/ burn the image to a CD or DVD], insert it into the system's optical drive, and ensure the system is configured to boot from the optical drive.
+#* If testing USB media on a real machine, prepare the USB stick according to [[How_to_create_and_use_Live_USB|the official instructions]], using the most prominently-recommended method (currently Fedora Media Writer), and ensure the system is configured to boot from the USB medium.
+# If the image you are installing from is a network install image, ensure the system has a working network connection.
 |actions=
-# Boot the system from the prepared optical or USB media.
+# Boot the system from the prepared install medium.
 # 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.
+# Once booted, run the installer (if necessary) and complete an installation using the default repository configuration.
+#* If the network connection requires configuration, configure it.
+#* Do not adjust the default repository configuration in any way.
+#* In order to improve the efficiency of [[QA:Release_validation_test_plan|release validation testing]], it's OK to change any other installation settings (disk layout, language, and so on) so the test run simultaneously covers this test case and some other test case. ''Any'' successful install attempt using the media under test and the default repository configuration can be considered a '''pass''' for this test. A '''fail''' should only be reported if any of the expected results below does not transpire.
 |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.
-# 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 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.
+#* Failures related to some particular ''installation configuration'', ''pre-existing disk content'' or ''system hardware or configuration'' are also likely out of scope for this test case (but may be a violation of one of the other release validation test cases). If ''any'' install attempt using the ''medium under test'' and the ''default repository configuration'' works, and the other conditions listed here are met, this test should be considered to have passed.
 # 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.
 }}
 [[Category:Installer Boot Methods]]
 [[Category:UEFI Test Cases]]
 [[Category:Installation Source]]
 [[Category:Package_anaconda_test_cases]]

Search

QA:Testcase Boot default install: Difference between revisions

Latest revision as of 18:53, 28 October 2016

Contents

Description

Setup

How to test

Expected Results