From Fedora Project Wiki

mNo edit summary
(Write a test case)
 
Line 1: Line 1:
{{Template:Associated_release_criterion|Basic|shutdown}}
{{Template:Associated_release_criterion|Basic|shutdown}}
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests if the system can be halted, rebooted or powered off by using CLI command to control the process.
|description=This test case tests if the system can be '''halted''', '''rebooted''' or '''powered off''' by using CLI command to control the process.
|actions=
|actions=
# Clean boot the Fedora you wish to test: this could be a system installed from a particular snapshot, pre-release, or release, or a live image. It should be an image for which updates will be available (or you can downgrade a package after installation).
# Clean boot the Fedora you wish to test: this could be a system installed from a particular snapshot, pre-release, or release, or a live image. It should be an image for which updates will be available (or you can downgrade a package after installation).
# Open a console, and run the command {{command|dnf update}} as root. If you have any difficulty opening a console in the normal fashion from the desktop you are testing, note this, but continue with the test. Complete the update process. If you encounter dependency problems, ensure a bug is reported for the issue, and try with a different package.
# Open a virtual console (press '''Ctrl-Alt-F2''').
# Login as the root user, or as a user with '''sudo''' rights.
# Halt the system using the `halt` command when logged in as root, or `sudo halt` otherwise.
# Reboot (restart) the system.
# Repeat previous steps, using the `reboot` and `poweroff` commands.
# Shut the running system down using the `shutdown now` command entered as a non-root user.
|results=
|results=
# The update process should complete successfully. Errors caused by packaging bugs should be reported to the individual packages, but would not usually count as release-blocking bugs in the updater itself.
# The system should accept all commands and show an adequate reaction.
# Using the `halt` command, the system goes down, but the machine stays on. You will be able to see the results of the process listed on the screen. All file-systems must be cleanly unmounted. No error messages should be listed. If you see an error message, report a bug.
# Using the `reboot` command, the system reboots without any user interaction and displays a login prompt (graphical or text).
# The system must boot without errors and all expected disk partititions and filesystems must be cleanly mounted.
# Using the `poweroff` and `shutdown now` commands makes the system go down and switches off the machine completely.
}}
}}

Latest revision as of 12:18, 1 February 2019

Note.png
Associated release criterion
This test case is associated with the Basic_Release_Criteria#shutdown 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 tests if the system can be halted, rebooted or powered off by using CLI command to control the process.


How to test

  1. Clean boot the Fedora you wish to test: this could be a system installed from a particular snapshot, pre-release, or release, or a live image. It should be an image for which updates will be available (or you can downgrade a package after installation).
  2. Open a virtual console (press Ctrl-Alt-F2).
  3. Login as the root user, or as a user with sudo rights.
  4. Halt the system using the halt command when logged in as root, or sudo halt otherwise.
  5. Reboot (restart) the system.
  6. Repeat previous steps, using the reboot and poweroff commands.
  7. Shut the running system down using the shutdown now command entered as a non-root user.

Expected Results

  1. The system should accept all commands and show an adequate reaction.
  2. Using the halt command, the system goes down, but the machine stays on. You will be able to see the results of the process listed on the screen. All file-systems must be cleanly unmounted. No error messages should be listed. If you see an error message, report a bug.
  3. Using the reboot command, the system reboots without any user interaction and displays a login prompt (graphical or text).
  4. The system must boot without errors and all expected disk partititions and filesystems must be cleanly mounted.
  5. Using the poweroff and shutdown now commands makes the system go down and switches off the machine completely.



Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_halt_reboot_shutdown&oldid=533041"