QA:Testcase desktop user switching

Click here to set up this language box

Associated release criterion
This test case is associated with the Fedora_40_Final_Release_Criteria#user-switching 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 user switching works correctly, i.e. it is possible, in case one user is logged in a system session, another user (or users) can log onto the system and use their own session in parallel with the first user without affecting the original session in any way.

User switching in this context does not represent switching between a desktop session and a virtual console, nor it represents using su or sudo commands to acquire different user identities on a terminal session.

How to test

1. Create a default installation of the Fedora release and flavor (Workstation, KDE) you wish to test.
2. Create two user accounts.
3. Clean boot the system.

Scenario 1

1. Log in with the first user account.
2. Check if the correct user has been logged in.
3. Open one or more applications.
4. Optionally open or create some content in them.
5. Use the system menu to switch users (switch users usually is located along reboot and shutdown menu items)
6. Log in with the second user account.
7. Open one or more applications and close them again.
8. Log out of the current session.
9. Log in with the first user account again.
10. Check that all applications are still running as they were before.
11. Close them and log out.

Scenario 2

1. Log in with the first user account.
2. Check if the correct user has been logged in.
3. Open one or more applications.
4. Optionally open or create some content in them.
5. Lock the screen using the menu or the keyboard shortcut.
6. Use switch user button to switch users.
7. Log in with the second user account.
8. Open one or more applications and close them again.
9. Log out of the current session.
10. Log in with the first user account again.
11. Check that all applications are still running as they were before.
12. Close them and log out.

Scenario 3

1. Log in with the first user account.
2. Check if the correct user has been logged in.
3. Open one or more applications.
4. Optionally open or create some content in them.
5. Switch to a different user.
6. Open one or more applications and close them again.
7. Log out of the current session.
8. Reboot the system.

Scenario 4 (optional)

1. Log in with the first user account.
2. Check if the correct user has been logged in.
3. Open one or more applications.
4. Optionally open or create some content in them.
5. Use the system menu to switch users.
6. Log in with the second user account.
7. Open one or more applications.
8. Switch between the two users several time and check the status of the sessions.
9. Finally, log out of both accounts.

Scenario 5 (optional)

1. Try switching more than two users.

Expected Results

1. When switching users, the second user must be able to log in and another desktop session must start and function fully.
2. When returning to a previous session, the particular user must be able to log back and the session's previous status-quo must be restored, i.e. all applications are still running as they were before the switch.
3. When trying to reboot or power-off a system with logged-in users, a warning message about possible consequences must appear and needs to be confirmed out before rebooting or powering off.
4. Problems with logging in and out, as well as with rebooting or powering off the system, are out of scope of this test, but they would automatically fail the QA:Testcase_desktop_login test case.