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
When starting cypress version 11.2.0 using npx cypress open, selecting a testing type and running a test, changes to the tests source file will trigger a new test run. When opening cypress using npx cypress open --e2e or npx cypress open --component changes to the test file will not trigger a rerun.
Desired behavior
Changes to the test file should automatically trigger a rerun independent of the testing type. As long as cypress is started using cypress open it should not make a difference if the test type is passed via a cli parameter or selected in the ui.
Test code to reproduce
The behaviour can be reproduced by just running npm i cypress in an empty folder, opening it using npx cypress open and automatically scaffolding the example e2e tests. When running one of them changes to its file will trigger a rerun. When cypress is closed and reopened udin npx cypress open --e2e this time changes will no longer cause a rerun.
Cypress Version
11.2.0
Node version
v16.16.0
Operating System
macOS 12.6
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered:
markbrockhoff
changed the title
Files are not watchen when running cypress open wit --component or --e2e
Files are not watched when running cypress open wit --component or --e2e
Nov 28, 2022
markbrockhoff
changed the title
Files are not watched when running cypress open wit --component or --e2e
Files are not watched when running cypress open with --component or --e2e
Nov 29, 2022
Hi @markbrockhoff , thanks for letting us know about this! I've confirmed this is a bug that's still present in 12.0.1 and will get this routed to the team to look into. It looks like there is a workaround by not passing a test mode on the CLI and selecting E2E or CT manually from the launchpad, but obviously that's not ideal and we want to get this fixed. Sorry for the inconvenience!
nagash77
added
E2E
Issue related to end-to-end testing
Triaged
Issue has been routed to backlog. This is not a commitment to have it prioritized by the team.
and removed
routed-to-e2e
labels
Apr 19, 2023
Current behavior
When starting cypress version 11.2.0 using
npx cypress open
, selecting a testing type and running a test, changes to the tests source file will trigger a new test run. When opening cypress usingnpx cypress open --e2e
ornpx cypress open --component
changes to the test file will not trigger a rerun.Desired behavior
Changes to the test file should automatically trigger a rerun independent of the testing type. As long as cypress is started using
cypress open
it should not make a difference if the test type is passed via a cli parameter or selected in the ui.Test code to reproduce
The behaviour can be reproduced by just running
npm i cypress
in an empty folder, opening it usingnpx cypress open
and automatically scaffolding the example e2e tests. When running one of them changes to its file will trigger a rerun. When cypress is closed and reopened udinnpx cypress open --e2e
this time changes will no longer cause a rerun.Cypress Version
11.2.0
Node version
v16.16.0
Operating System
macOS 12.6
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered: