From Fedora Project Wiki

No edit summary
(link to tracker issues)
 
(8 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case focuses on lock screen, shown when user session is locked.
|description=This test case focuses on the lock screen. This is the screen that is shown when user session is locked, which allows unlocking.
 
|setup=
|setup=
* Login to Gnome Shell.
 
|actions=
|actions=
# Lock user session using "User menu" - "Lock" or keyboard shortcut "Ctrl" + "Alt" + "L".
# Log in to the GNOME desktop.
# Slide screen upward by your finger or mouse, or hit "Escape" or "Enter" key. Enter correct password to unlock user session.
# Run some application, so that you can determine this session from a fresh new session (e.g. open a file browser or a text editor).
# Try unlock session using wrong password.
# Lock the user session. You have the following options of manual locking:
# Try "Log in as another user" option.
#* from the system menu (top right corner)
# In "User menu" - "System Settings" - "Brightness & Lock" you can configure inactivity after then screen turns off and lock delay. Check "Show notifications when locked" to enable notifications on lock screen.
#* with the <code>Super+L</code> keyboard shortcut
#* by searching for ''Lock Screen'' (or your local translation) item in the GNOME overview and clicking on it
# Wait for the screen to turn off.
# Wake up the screen by pressing a key or moving the pointer. You should see a lock screen containing current time and date.
# Try to unlock the session using wrong password. The screen should stay locked and show an error message.
# Unlock the session using the correct password. You should be back at your existing session with your running application.
# Lock the session again using a different method (see the list above).
# This time, click the ''"Log in as another user"'' button, you should be redirected to the login screen with a list of all available user accounts.
# Log in to your original account by selecting it and providing the correct password. You should be back at your existing session with your running application.
# If there are still some locking methods you haven't tried (see the list above), test the remaining methods one by one. Lock the desktop, then unlock it, and you should be back at your existing session with your running application.
# Go to ''Settings -> Privacy -> Screen Lock'', and notice how long it takes for your system to blank the screen and then lock the screen. For testing purposes, you can lower that value to a minimum.
# Stop interacting with the desktop (no mouse movement, keyboard presses, etc) and measure the time. After the interval specified above, your screen should turn off and your session should lock. Move your mouse or press a keyboard key to verify that the screen is really locked.
# Unlock the screen. You should be back at your existing session with your running application.
|results=
|results=
# You should see actual time and date.
# All attempted operations should finish successfully.
# Screen should unlock.
# When the screen is locked, it mustn't be possible to access your user session.
# Screen should stay locked and show error message.
# Please report all failures to the [https://gitlab.gnome.org/GNOME/gnome-shell/issues GNOME tracker].
# "Log in as another user" option should bring you to Gnome Login Screen with list of all available accounts. Then you can switch back or login as another user.
# Screen should turn off and lock after configured time. Notifications should be visible on locked screen.
}}
}}
[[Category:Package_gnome-shell_test_cases]]
[[Category:Package_gnome-shell_test_cases]]
[[Category:GNOME3_acceptance_test_cases]]
[[Category:GNOME desktop feature test cases]]

Latest revision as of 11:05, 8 March 2023

Description

This test case focuses on the lock screen. This is the screen that is shown when user session is locked, which allows unlocking.


How to test

  1. Log in to the GNOME desktop.
  2. Run some application, so that you can determine this session from a fresh new session (e.g. open a file browser or a text editor).
  3. Lock the user session. You have the following options of manual locking:
    • from the system menu (top right corner)
    • with the Super+L keyboard shortcut
    • by searching for Lock Screen (or your local translation) item in the GNOME overview and clicking on it
  4. Wait for the screen to turn off.
  5. Wake up the screen by pressing a key or moving the pointer. You should see a lock screen containing current time and date.
  6. Try to unlock the session using wrong password. The screen should stay locked and show an error message.
  7. Unlock the session using the correct password. You should be back at your existing session with your running application.
  8. Lock the session again using a different method (see the list above).
  9. This time, click the "Log in as another user" button, you should be redirected to the login screen with a list of all available user accounts.
  10. Log in to your original account by selecting it and providing the correct password. You should be back at your existing session with your running application.
  11. If there are still some locking methods you haven't tried (see the list above), test the remaining methods one by one. Lock the desktop, then unlock it, and you should be back at your existing session with your running application.
  12. Go to Settings -> Privacy -> Screen Lock, and notice how long it takes for your system to blank the screen and then lock the screen. For testing purposes, you can lower that value to a minimum.
  13. Stop interacting with the desktop (no mouse movement, keyboard presses, etc) and measure the time. After the interval specified above, your screen should turn off and your session should lock. Move your mouse or press a keyboard key to verify that the screen is really locked.
  14. Unlock the screen. You should be back at your existing session with your running application.

Expected Results

  1. All attempted operations should finish successfully.
  2. When the screen is locked, it mustn't be possible to access your user session.
  3. Please report all failures to the GNOME tracker.