QA:Testcase base startup

From FedoraProject

Jump to: navigation, search
Note.png
Associated release criterion
This test case is associated with the Fedora_26_Alpha_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.
Note.png
Associated release criterion
This test case is associated with the Fedora_26_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.


Contents

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

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.