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
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: