You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In some edge cases (stopping and restarting the Cypress Test Runner tests multiple times) will cause the Cypress time travel logs to be printed in the next test.
To Reproduce
Start the Cypress Test runner (npx cypress open)
Run the tests
Leave to run for 1 or 2 tests to finish
Stop and restart the tests
Do this 3-4-5 times
At some point the Time Travel Logs from Test#1 are printed in Test#2
Expected behavior
The logs should always be printed in the test they belong to, not the following one.
** Operating system, Node.js an npm versions, or browser version (please complete the following information):**
OS: Windows
Node.js: 14.16
npm: 6.14
Browser: Electron
The text was updated successfully, but these errors were encountered:
Unfortunately, "edge cases" are hard to reproduce, and I haven't achieved it. Anyway, I won't close the issue, because I suspect it could be related to the internal usage of beforeEach and afterEach hooks. I have planned to refactor the plugin to use other Cypress events if possible in order interfere as less as possible with test definitions. So, when the new release is ready I will add a comment here to check if the issue still happens.
Describe the bug
In some edge cases (stopping and restarting the Cypress Test Runner tests multiple times) will cause the Cypress time travel logs to be printed in the next test.
To Reproduce
Expected behavior
The logs should always be printed in the test they belong to, not the following one.
** Operating system, Node.js an npm versions, or browser version (please complete the following information):**
The text was updated successfully, but these errors were encountered: