This test case checks the basic boot process.
How to test
- Perform a clean, graphical installation of the Fedora release you wish to test
- Boot the installed system
- Shut down the system
- Boot the installed system with each of the following kernel parameters, in turn: 1, 2, 3, 4, 5, single, S, s, -s. During one of the single user mode boots, exit single user mode and observe the result. Try both shutdown and reboot operations in between boots
- Configure the system to boot to console (runlevel 3), using the recommended method for the initialization system in use (for systemd, run the command
ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target), and reboot the system with none of the above kernel parameters
- The first boot of the installed system should boot to a graphical login manager, and the graphical login sequence should be displayed during boot (if the tested system configuration is capable of it)
- Booting with kernel parameters 1, 2, 3, 4 and 5 should boot to those runlevels, or their equivalents under an init system that does not implement runlevels directly. Booting with kernel parameters 1, single, S, s or -s should boot to single user mode (and this mode should be usable). You can use
who -rto check current runlevel.
- Exiting single user mode should result in the system returning to the default boot state
- The system should correctly boot to a console when configured to do so
- When booted to console mode, six gettys should be run, on tty1-6 (so ctrl-alt-f1 through ctrl-alt-f6 should all lead to separate, numbered login prompts). When booted to graphical mode, five gettys should be run, on tty2-6, and X should be started on a different tty (usually 1 or 7)
- System boot, shutdown and restart operations should be logged by ConsoleKit (in