#630 Create a test case for User Switching criterion
Closed: Fixed 4 years ago by kparal. Opened 4 years ago by kparal.

With the freshly minted user switching criterion, we need to create a test case for it. Looking for volunteers! :wink:


Metadata Update from @lruzicka:
- Issue assigned to lruzicka

4 years ago

So, it is "looking for volunteers" :ticket: after all. I am taking it then.

I created a draft of the test case. I suggest 5 different scenarios (two of them optional). For automation, I would use the first three scenarios.

Please, comment.

https://fedoraproject.org/wiki/QA:Testcase_desktop_user_switching

Awesome, thanks Lukas! Here are my thoughts:

  • The hyperlink in "Associated release criterion" box is broken.
  • In Description, I'd also specify that user switching for this purpose doesn't include switching between different desktop environments.
  • The first 3 steps in How To Test section should be instead in Setup section.
  • I was confused why Scenario 1 and Scenario 3 are almost identical, and why you don't check the first user session at the end of Scenario 3. Only after reading Excepted Results I realized the purpose of Scenario 3 is to check the existence of a warning dialog during reboot when some users are still logged in. This is very obscure and testers will not find it this way. Scenario 3 needs to include an additional step, e.g. "Observe a warning dialog informing you that the first user is still logged in and his session data might be lost. Confirm the reboot".
  • I'd like to merge Scenario 1 and 4. They are the same, just the switch is performed multiple times in the latter one. And I think that should be the base scenario anyway. I definitely don't consider that optional, if I can't switch between user A and B repeatedly, it's a clear violation of the criterion (and breakage of the most common home use case).
  • I'd somewhat rephrase Scenario 2. In previous GNOME version, IIRC, you could switch users from the running session, from the lock screen or from the login screen, so 3 options. I haven't checked current KDE. But the options will come and go, the UI will change. In this scenario, I'd ask the tester to identify all screen from which a user switch can be performed (e.g. running session, lock screen, login screen) and test user switching from all these screens.
  • I'd create a new Scenario where I'd ask the tester to log in with the first user, and the repeatedly log in and log out the second user several times. Then check the first user's session.

So with these changes, we have:
1. A scenario where user switching is tested multiple times, using running-session switch buttons.
2. A scenario where all "alternative" user switching UI options are tested, like lock screen and login screen switch buttons.
3. A scenario where a single user is logged in the whole time, and the second user keeps logging in and out.
4. An optional scenario with more than two users.

WDYT?

Yes, I think it sounds reasonable. I have updated the draft.

I made some changes to the page. Please see
https://fedoraproject.org/w/index.php?title=QA:Testcase_desktop_user_switching&action=history
and inspect them (each change is made as a separate revision with justification).

If you like the changes, I believe you can add this to the
https://fedoraproject.org/wiki/Template:Desktop_test_matrix
and update References in
https://fedoraproject.org/wiki/Fedora_33_Final_Release_Criteria#user-switching
(please refer to this ticket when saving both pages)

Thanks!

It's fine. I am just not sure that I understand what Scenario 5 is about. Who exactly are users without password and how can they log onto the system? Are you talking about users created via Gnome Settings with no password initially and users needing to set the password upon the first login? If so, please note that this approach currently does not, and, in the nearest future, will not work in KDE.

No, I'm really talking about password-less users. Users with an empty password, that's perhaps clearer? Those can't be created in gnome-control-center, but you can create them on a command line or in Everything netinst (and I assume even in KDE Settings, because KDE tries to not limit any of your options). Empty passwords are popular for home PC use cases (I can't comprehend why GNOME doesn't allow to create them, but that's a different debate). How would you phrase the text to make it clearer?

Metadata Update from @kparal:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Log in to comment on this ticket.

Metadata