Project

General

Profile

action #40490

action #40484: [functional][u][epic] Move different checks to separate test suites not to affect other functional tests

[functional][u] Implement test for screensaver and disable it in other scenarios

Added by riafarov over 1 year ago. Updated 20 days ago.

Status:
Workable
Priority:
Normal
Assignee:
Category:
New test
Target version:
SUSE QA tests - Milestone 31
Start date:
2018-08-31
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:
Duration:

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)

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

Related issues

Related to openQA Tests - action #45710: [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays)Resolved2019-01-042019-02-08

Related to openQA Tests - action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlockRejected2018-11-21

Related to openQA Tests - action #40094: [functional][u] xscreensaver disabled in updates_packagekit_gpk.pm is back in x11 testsRejected2018-08-22

Related to openQA Tests - action #57404: [functional][u] opensuse maintenance test fails in disable_screensaverResolved2019-09-26

Related to openQA Tests - action #64812: [functional][u][sporadic] test fails in shutdown - Screen buffer shows old display state instead of locked screen, ensure_unlocked_desktop thinks it is unlocked and test fails laterWorkable2020-03-25

History

#1 Updated by okurz over 1 year 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

#2 Updated by okurz over 1 year ago

  • Target version set to Milestone 20

#3 Updated by okurz over 1 year ago

  • Target version changed from Milestone 20 to future

#4 Updated by okurz over 1 year 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

#5 Updated by okurz over 1 year ago

  • Due date set to 2019-05-07
  • Target version changed from future to Milestone 24

#6 Updated by okurz over 1 year ago

  • Related to action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock added

#7 Updated by okurz about 1 year ago

  • Related to action #40094: [functional][u] xscreensaver disabled in updates_packagekit_gpk.pm is back in x11 tests added

#8 Updated by okurz about 1 year ago

  • Due date changed from 2019-05-07 to 2019-06-04
  • Target version changed from Milestone 24 to Milestone 25

#9 Updated by riafarov 12 months ago

  • Due date deleted (2019-06-04)

#10 Updated by mgriessmeier 12 months ago

  • Status changed from New to Workable
  • Priority changed from Normal to High

#11 Updated by szarate 11 months ago

  • Assignee set to szarate

#12 Updated by mgriessmeier 11 months ago

  • Target version changed from Milestone 25 to Milestone 26

#13 Updated by mgriessmeier 9 months ago

  • Target version changed from Milestone 26 to Milestone 27

#14 Updated by szarate 9 months ago

  • Assignee deleted (szarate)

#15 Updated by dheidler 9 months ago

  • Status changed from Workable to In Progress
  • Assignee set to dheidler

#16 Updated by dheidler 9 months ago

  • Status changed from In Progress to Feedback

#17 Updated by mgriessmeier 9 months ago

  • Target version changed from Milestone 27 to Milestone 28

waiting for PR review

#18 Updated by SLindoMansilla 8 months ago

  • Related to action #57404: [functional][u] opensuse maintenance test fails in disable_screensaver added

#19 Updated by dheidler 8 months 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?

#20 Updated by szarate 7 months 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.

#21 Updated by szarate 6 months 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

#22 Updated by mgriessmeier 5 months ago

  • Target version changed from Milestone 28 to Milestone 31

#23 Updated by mgriessmeier 5 months ago

  • Priority changed from High to Normal

#24 Updated by SLindoMansilla about 1 month ago

  • Assignee set to szarate

#25 Updated by SLindoMansilla 20 days ago

  • Related to action #64812: [functional][u][sporadic] 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

Also available in: Atom PDF