action #40490
Updated by szarate over 3 years ago
## Motivation See general motivation in the parent ticket. We have a lot of code to detect screensaver, and then do additional steps in order to get to the SUT. This makes testing more complex and less stable. Not to lose any coverage, we should implement separate tests which assures screensaver work. And then disable it for other scenarios (e.g. all x11 tests) See https://bugzilla.suse.com/show_bug.cgi?id=1168979 (which bites us quite often) ## Acceptance criteria 1. screensaver functionality is tested for different desktops for all distris under development 2. screensaver is disabled for all other scenarios which it can impact ## Suggestions 1. Ensure that the disable screensaver module is schedule right after the first module