QA:Testcase desktop login

From FedoraProject

Jump to: navigation, search
Note.png
Associated release criterion
This test case is associated with the Fedora_22_Alpha_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.
Note.png
Associated release criterion
This test case is associated with the Fedora_22_Beta_Release_Criteria#desktop-shutdown-reboot-logout 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 whether the desktop log in, log out and shutdown operations work correctly.


How to test

  1. Do a default installation of the Fedora release you wish to test. Create two user accounts.
  2. Clean boot the system, and note what accounts are listed on the login screen.
  3. Log in with the first user account.
  4. Log out of the desktop.
  5. Log in with the second user account.
  6. Log out.
  7. Try to log in with either account, intentionally entering the wrong password.
  8. Test alternative actions - such as shut down, suspend, and restart - instead of logging in, if they are offered in the release being tested.
  9. Log in with any account, and test all session management (log out, shut down, reboot, suspend etc.) activities offered by the desktop.

Expected Results

  1. The login manager should display all regular user accounts, but not the root account, for selection.
  2. You should be able to log in with each configured user account and the correct password.
  3. You should be able to perform all session management activities offered by the desktop.
  4. Entering an incorrect password should return you to the account selection stage, with a warning/explanation message.
  5. The alternative actions (shut down, restart, suspend etc) should behave as expected.