action #40490
closedcoordination #40484: [qe-core][functional][epic] Move different checks to separate test suites not to affect other functional tests
[qe-core][functional] Implement test for screensaver and disable it in other scenarios
Added by riafarov over 6 years ago. Updated 8 months ago.
0%
Description
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¶
- screensaver functionality is tested for different desktops for all distris under development
- screensaver is disabled for all other scenarios which it can impact
Suggestions¶
- Ensure that the disable screensaver module is schedule right after the first module
Updated by okurz over 6 years ago
- Subject changed from [functional] Implement test for screensaver and disable it in other scenarios to [functional][u] Implement test for screensaver and disable it in other scenarios
- Category set to Enhancement to existing tests
Updated by okurz about 6 years ago
- Target version changed from Milestone 20 to future
Updated by okurz almost 6 years ago
- Related to action #45710: [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays) added
Updated by okurz almost 6 years ago
- Due date set to 2019-05-07
- Target version changed from future to Milestone 24
Updated by okurz almost 6 years ago
- Related to action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock added
Updated by okurz almost 6 years ago
- Related to action #40094: [functional][u] xscreensaver disabled in updates_packagekit_gpk.pm is back in x11 tests added
Updated by okurz almost 6 years ago
- Due date changed from 2019-05-07 to 2019-06-04
- Target version changed from Milestone 24 to Milestone 25
Updated by mgriessmeier over 5 years ago
- Status changed from New to Workable
- Priority changed from Normal to High
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 25 to Milestone 26
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 26 to Milestone 27
Updated by dheidler over 5 years ago
- Status changed from Workable to In Progress
- Assignee set to dheidler
Updated by dheidler over 5 years ago
- Status changed from In Progress to Feedback
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 27 to Milestone 28
waiting for PR review
Updated by SLindoMansilla about 5 years ago
- Related to action #57404: [functional][u] opensuse maintenance test fails in disable_screensaver added
Updated by dheidler about 5 years ago
- Assignee changed from dheidler to mgriessmeier
After the 2nd try I'm not sure if we can easily implement this - at least before we introduced YAML scheduling.
This seems to have too many side effects.
@Matthias: should we keep this ticket or reject it?
Updated by szarate about 5 years ago
- Category changed from Enhancement to existing tests to New test
- Status changed from Feedback to New
- Assignee deleted (
mgriessmeier)
While looking at this ticket with Sergio
Suggestions are:
- Split deactivating the screen saver and testing the screen saver into separate modules
- create a test matrix to allow proper verification when it is implemented, since a reason for a revert, were the QAM tests.
Updated by szarate about 5 years ago
- Status changed from New to Workable
- Estimated time set to 42.00 h
Setting to workable, as we agreed at some point I'll do the matrix/table
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 28 to Milestone 31
Updated by mgriessmeier almost 5 years ago
- Priority changed from High to Normal
Updated by SLindoMansilla over 4 years ago
- Related to action #64812: [qe-core][functional][sporadic][needs-refining] test fails in shutdown - Screen buffer shows old display state instead of locked screen, ensure_unlocked_desktop thinks it is unlocked and test fails later added
Updated by SLindoMansilla over 4 years ago
Updated by tjyrinki_suse about 4 years ago
- Subject changed from [functional][u] Implement test for screensaver and disable it in other scenarios to [qe-core][functional] Implement test for screensaver and disable it in other scenarios
Updated by szarate almost 4 years ago
- Description updated (diff)
- Assignee deleted (
szarate)
Updated by tjyrinki_suse almost 4 years ago
- Target version changed from Milestone 31 to QE-Core: Ready
Updated by tjyrinki_suse almost 4 years ago
- Target version changed from QE-Core: Ready to Ready
Updated by szarate almost 4 years ago
- Target version changed from Ready to QE-Core: Ready
Updated by tjyrinki_suse almost 4 years ago
- Target version changed from QE-Core: Ready to future
Updated by slo-gin over 2 years ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin 9 months ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by mgrifalconi 8 months ago
- Tags set to qecore-cleanup
- Status changed from Workable to Rejected