3.36 login / unlock testing
The shell has a new login and unlock design for 3.36. Login and unlock are complex, and the changes were merged relatively late in the development cycle. We are therefore pushing to do as much testing as possible before the 3.36.0 release. Please help!
This isn't really a technical issue so apologies if it's the wrong place to put it.
Ways to run the latest GNOME Shell:
- Install Fedora 31 in a VM, and build from source (instructions)
- Install a Fedora 32 nightly image (best to do this in a VM)
- Use a nightly GNOME image with Boxes
If anyone knows more methods to run the development version of GNOME shell, please provide details.
- Once you have a working testing setup, run through the tests below.
- Problems discovered during testing should be reported as issues.
- As an optional step, you can provide a report on your tests in the comments below, using this template.
- There are various conditions and configurations which can be used for testing (see the test conditions section). Where possible, try re-running the test under different conditions.
- Please use the comments if you have questions or comments about the test setup and/or plan.
|1||Login with password||Should be able to boot, select a user, then login.|
|2||Lock the screen||All the methods to lock the screen should work: system menu, Super+L shortcut, search for "lock".|
|3||Unlock with password||Should be able to wake up the screen, enter a password, and get back to the user session|
|4||Unlock with fingerprint||Successful unlock with a fingerprint reader – should be possible from the initial “clock” screen.|
|5||Unlock with smartcard||Successful unlock with a smartcard – should be possible from the initial “clock” screen.|
|6||Unsuccessful auth with password||Incorrect entry of a password should result in the correct error message being shown and the password entry continuing to be shown.|
|7||Unsuccessful auth with fingerprint||Incorrect finger or finger placement should result in meaningful feedback, in both the clock and the authentication view.|
|8||Unsuccessful auth with smartcard||Incorrect smartcard presentation should result in meaningful feedback, in both the clock and the authentication view.|
|9||Change wallpaper||The lock screen background should be a blurred version of the lock screen wallpaper. The background should update to reflect lock screen wallpaper changes.|
|10||Empty password field||Pressing return when the password field is empty should result in meaningful feedback.|
|11||Select a user by entering a username||After boot, select "Not listed?", enter your username and password and login.|
|12||Unsuccessful select user by username||Try to login with an incorrect username: appropriate feedback should be given.|
|13||Cancel select user by username||From the user list, select "Not listed?", then press back, select a user from the list and successfully login. This should work whether text has been entered in the username entry or not.|
|14||Select a user while user account changes take place||Open the user list: what happens if user accounts are added or removed?|
|15||Cancel login||Select a user, try to login, fail, go back to the user list.|
|16||Cancel unlock||Wake up the screen, try to unlock, fail, lock the screen again (screen should blank).|
|17||Switch user||Use “switch user” from the system menu – should open the user list and allow login with a different account.|
|18||Log in as another user from the lock screen||When locked, wake up the screen, navigate to the user list, select a user, successfully log in with a different user account.|
|19||Session menu||User should be able to successfully select a session from the session menu, prior to login.|
|20||Notifications||Unseen notifications should be listed on the lock screen. Test with:
|21||Urgent notifications||Urgent notifications should be shown on the lock screen and should be visually emphasised. Can be tested by running
|22||Last login message||Currently unclear how to test this.|
|23||Automatic login||If automatic login is enabled, after boot login should be skipped and the session should start.|
|24||Set user password on first login||Create a user in Settings, and set “allow to set password on first login”. Then login with that user and set a password.|
|25||Timed login||Currently unclear how to test this.|
|26||Accessibility menu||It should be possible to enable accessibility features during login.|
|27||Input source switching||It should be possible to switch input source during login.|
Different ways that the tests can be run:
- Number of user accounts: 1 / many
- Input: pointer / keyboard / touchscreen
- Typing method: physical keyboard / on-screen keyboard
- High-contrast mode
- Classic mode
- Large text mode
- Screen reader
- Right-to-left locale