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

Cypress Executor is crashing upon using modifyObstructiveCode:false #28304

Closed
abhiskkk-mp opened this issue Nov 10, 2023 · 3 comments
Closed
Labels
stale no activity on this issue for a long period

Comments

@abhiskkk-mp
Copy link

Current behavior

My AUT is having multiple frames on the web pages. Taking reference from the older issue (here) I passed modifyObstructiveCode:false in the config file. Now when trying to run the cypress executor, the application is crashing and returning to the spec selection page every time.

If I remove the modifyObstructiveCode then the spec is executing but my frames are loading in Cypress by replacing window.parent by window.self. Hence the locators are not identified as expected.

Thanks

Desired behavior

The frames should load with window.parent only without crashing the executor so that the test runs smoothly.

Test code to reproduce

N/A (Can share more details as required)

Cypress Version

10.8

Node version

16.15.1

Operating System

WIN

Debug Logs

No response

Other

No response

@abhiskkk-mp
Copy link
Author

Added new issue as asked @jennifer-shehane

@cypress-app-bot
Copy link
Collaborator

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

@cypress-app-bot cypress-app-bot added the stale no activity on this issue for a long period label May 9, 2024
@cypress-app-bot
Copy link
Collaborator

This issue has been closed due to inactivity.

@cypress-app-bot cypress-app-bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale no activity on this issue for a long period
Projects
None yet
Development

No branches or pull requests

2 participants