From Fedora Project Wiki

(add another criterion)
(revise to drop encryption stuff (duped from QA:Testcase_partitioning_guided_encrypted) and adjust for Products and non-installer images)
Line 4: Line 4:
{{Template:Associated_release_criterion|Alpha|self-identification}}
{{Template:Associated_release_criterion|Alpha|self-identification}}
{{Template:Associated_release_criterion|Final|artwork}}
{{Template:Associated_release_criterion|Final|artwork}}
{{Template:Associated_release_criterion|Final|keyboard-layout-configuration}}


{{QA/Test_Case
{{QA/Test_Case
|description=This test case checks whether an installed Fedora system boots successfully to a usable state.
|description=This test case checks whether an installed Fedora system boots successfully to a usable state.
|setup=Perform an installation of the Fedora release you wish to test, in graphical mode. Follow all defaults, with the exception that you should encrypt a system partition (e.g. the root partition). Note that the test case [[QA:Testcase_Anaconda_autopart_(encrypted)_install]] covers this process: failures in it are a failure for that test case, not this one. Create a user account during installation. Again, this stage constitutes another test case, [[QA:Testcase_Anaconda_user_creation]]. Once the test is complete, re-install with a non-graphical package set (e.g. Minimal), and repeat the test.
|setup=Install or deploy the Fedora release media you wish to test. Follow all defaults. Create a user account during installation or in the initial-setup utility. The User creation step is covered by other test cases, [[QA:Testcase_Anaconda_user_creation]] or [[QA:Testcase base initial setup]] - if you encounter problems with user creation, mark them as a failure of the appropriate test case.
|actions=
|actions=
# Boot into the installed system
# Boot into the installed system
# Enter the password for the encrypted partition if prompted
# Observe the result of the boot process
# Observe the result of the boot process
# Observe any graphics displayed during the boot process prior to the login manager: bootloader menu, graphical boot screen
# Observe any graphics displayed during the boot process prior to the login manager: bootloader menu, graphical boot screen
Line 17: Line 15:
# Observe the background used on the desktop (if reached)
# Observe the background used on the desktop (if reached)
|results=
|results=
# The system should prompt for the password for the encrypted partition and correctly unlock it when the password is entered (if this step fails, the boot will not complete correctly)
# Aside from accessing encrypted partitions if any are used, and the 'initial setup' utility on the first boot if it runs, no input should be required from the user for the boot process to complete
# Aside from this, no input should be required from you for the boot process to complete
# After installation/deployment of a system with a graphical desktop, the boot process should result in a usable graphical environment (either automatically logging into a working desktop environment, or presenting a login manager)
# After the graphical installation and user creation, the boot process should result in a usable graphical environment (either automatically logging into a working desktop environment, or presenting a login manager)
# After installation/deployment of a system with no graphical desktop, the boot process should leave you at a console with a working login prompt. If it does not, test whether you can at least access a working login prompt by switching to a different virtual terminal, with {{key press|Ctrl|Alt|F2}}, {{key press|Ctrl|Alt|F3}} etc.
# After the text installation and user creation, the boot process should leave you at a console with a working login prompt. If it does not, test whether you can at least access a working login prompt by switching to a different virtual terminal, with {{key press|Ctrl|Alt|F2}}, {{key press|Ctrl|Alt|F3}} etc.
# If the artwork used at the bootloader screen, during graphical boot, on the login manager, or the desktop background references a release number and/or pre-release phase (Alpha, Beta etc), it must be the current number and/or phase for the release or pre-release under test
# If the artwork used at the bootloader screen, during graphical boot, on the login manager, or the desktop background references a release number and/or pre-release phase (Alpha, Beta etc), it must be the current number and/or phase for the release or pre-release under test
# If the release being tested is a final release or post-Beta pre-release build, the artwork used in the login manager and on the default desktop (particularly the background) must be the correct and current artwork proposed for the release in question by the design team. If a background or artwork used in the bootloader menu screen or the graphical boot it must be either entirely generic (such as the Fedora logo) or part of the correct and current proposed artwork
# If the release being tested is a final release or post-Beta pre-release build, the artwork used in the login manager and on the default desktop (particularly the background) must be the correct and current artwork proposed for the release in question by the design team. If a background or artwork used in the bootloader menu screen or the graphical boot it must be either entirely generic (such as the Fedora logo) or part of the correct and current proposed artwork
}}
}}
[[Category:Base Acceptance Test Cases]]
[[Category:Base Acceptance Test Cases]]

Revision as of 18:47, 2 October 2014

Associated release criterion
This test case is associated with the Basic_Release_Criteria#expected-installed-system-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 Fedora_42_Beta_Release_Criteria#expected-installed-system-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#desktop-background 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#self-identification 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#artwork 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 checks whether an installed Fedora system boots successfully to a usable state.

Setup

Install or deploy the Fedora release media you wish to test. Follow all defaults. Create a user account during installation or in the initial-setup utility. The User creation step is covered by other test cases, QA:Testcase_Anaconda_user_creation or QA:Testcase base initial setup - if you encounter problems with user creation, mark them as a failure of the appropriate test case.

How to test

  1. Boot into the installed system
  2. Observe the result of the boot process
  3. Observe any graphics displayed during the boot process prior to the login manager: bootloader menu, graphical boot screen
  4. Observe the background used in the login manager screen (if any)
  5. Observe the background used on the desktop (if reached)

Expected Results

  1. Aside from accessing encrypted partitions if any are used, and the 'initial setup' utility on the first boot if it runs, no input should be required from the user for the boot process to complete
  2. After installation/deployment of a system with a graphical desktop, the boot process should result in a usable graphical environment (either automatically logging into a working desktop environment, or presenting a login manager)
  3. After installation/deployment of a system with no graphical desktop, the boot process should leave you at a console with a working login prompt. If it does not, test whether you can at least access a working login prompt by switching to a different virtual terminal, with Ctrl+Alt+F2, Ctrl+Alt+F3 etc.
  4. If the artwork used at the bootloader screen, during graphical boot, on the login manager, or the desktop background references a release number and/or pre-release phase (Alpha, Beta etc), it must be the current number and/or phase for the release or pre-release under test
  5. If the release being tested is a final release or post-Beta pre-release build, the artwork used in the login manager and on the default desktop (particularly the background) must be the correct and current artwork proposed for the release in question by the design team. If a background or artwork used in the bootloader menu screen or the graphical boot it must be either entirely generic (such as the Fedora logo) or part of the correct and current proposed artwork
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_base_startup&oldid=390193"