Closed rakeshnambiar closed 1 year ago
Well, this is one of Cypress' main and well documented drawbacks. You can work around this by diasbling webSecurity in Chrome. https://docs.cypress.io/guides/guides/web-security.html#Set-chromeWebSecurity-to-false
And the usual suggestion is to not test the login via the ui.
Thanks @Narretz That helps .. I am from Protractor-selenium background and new to Cypress :)
Hi @Narretz sorry for the delayed feedback. I tried this with the "chromeWebSecurity": false,
and getting the below mentioned error. This is not just to test the login feature. Instead I need to claim an article after login to the ORCID as part of the E2E flow. I also found the external application where I have this issue is developed in angular 11
.
Here's the UI flow in case you wish to take a look:
Start
buttonPlease note, I am using the latest version 9.1.1
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
Writing E2E tests is almost impossible due to the restriction while navigating to an integrated system. Test flow:
Sign in with ORCID
buttonError message
Desired behavior
Other tools like Selenium or protractor support to interact with the elements on the newly navigated page.
Test code to reproduce
Versions
"cypress": "^6.2.1"