QA:Testcase desktop login

In other languages: English (en) italiano (it) русский (ru) [edit]

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.

Associated release criterion
This test case is associated with the Fedora_42_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, particularly regarding keymaps.

How to test

Non-ascii characters are not allowed in password
In system-config-users or firstboot tools you can't create passwords containing non-ascii characters. That is tracked by RHBZ #646876.

Testing with just a US keyboard?
While helpful, different physical keyboard layouts are not required to complete this test. If you only have a US keyboard, you may test by selecting a UK keyboard layout and entering a character not found on a US keyboard, such as £ (Shift-3).

1. Do a default installation of the Fedora release you wish to test, but selecting a keyboard mapping which differs from the default. Create two user accounts, using characters in both username and password whose location is different in the selected mapping, as compared to US English
2. Clean boot the system, and note what accounts are listed on the login screen
3. Log in with the first user account, entering the variant characters using the keyboard mapping selected during installation
4. Check the selected keyboard mapping at the desktop
5. Log out of the desktop
6. Log in with the second user account, entering the variant characters using the keyboard mapping selected during installation
7. Log out
8. Try to log in with either account, intentionally entering the wrong password
9. Test alternative actions - such as shut down, suspend, and restart - instead of logging in, if they are offered in the release being tested
10. 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
6. Character entry during login should use the keymap selected during installation, not the default keymap (which is usually US English)
7. The keymap selected at the desktop following login should also be the keymap selected during installation