Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test runner re-runs automatically after screen unlock #23513

Open
emidhun opened this issue Aug 23, 2022 · 4 comments
Open

Test runner re-runs automatically after screen unlock #23513

emidhun opened this issue Aug 23, 2022 · 4 comments
Labels
Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. type: bug

Comments

@emidhun
Copy link

emidhun commented Aug 23, 2022

Current behavior

The test runner re-runs the spec after unlocking the screen.

Desired behavior

Previous test results should be there on the test runner after the unlocking of the screen followed by locking.

Test code to reproduce

Any spec

Cypress Version

10.3.1

Node version

v14.17.3

Operating System

macOS 12.4

Debug Logs

No response

Other

No response

@nagash77
Copy link
Contributor

@emidhun Can you provide more information about which browser you are seeing this behavior in? Can you try others to see if they behave the same?

Does the problem happen regardless of how long the screen is locked? Do you see this when you lock the screen for a couple seconds? A half hour?

@nagash77 nagash77 self-assigned this Aug 24, 2022
@emidhun
Copy link
Author

emidhun commented Sep 1, 2022

@nagash77 Regardless of the time spec restart after each unlocking of the screen.
Browser: Chrome104
Tested on different mac systems.

@emidhun
Copy link
Author

emidhun commented Sep 1, 2022

Steps to reproduce:

  • Set screen timeout (time to lock the screen) to a lesser number.
  • Open test runner and run the spec (It could be partial/ completed state)
  • Wait till the screen gets locked.
  • Unlock the screen.

@nagash77 nagash77 assigned lmiller1990 and unassigned nagash77 Sep 6, 2022
@lmiller1990
Copy link
Contributor

I reproduced it. I set my screen to lock after 1 minute and did the above. It was not 100% consistent but I saw it for E2E and CT.

@nagash77 nagash77 added CT Issue related to component testing Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. and removed routed-to-ct labels Apr 19, 2023
@lmiller1990 lmiller1990 removed their assignment Jun 28, 2023
@jennifer-shehane jennifer-shehane added type: bug and removed CT Issue related to component testing labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. type: bug
Projects
None yet
Development

No branches or pull requests

4 participants