-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Cross-origin Testing #17336
Comments
Is there any update on this? |
Any update on this since this is a most awaited feature to have in cypressIO? |
The work for this is in progress. There's a lot of work required and you can track all work in this branch: https://github.com/cypress-io/cypress/tree/feature-multidomain?rgh-link-date=2021-07-14T18%3A40%3A41Z |
Really need this for testing a Firebase Auth flow. 😁 Hoping we see a release soon. |
waiting for supporting several domains! |
Do you have some estimation, when this feature is going to be delivered? The code is a complete mess without it and everyone who uses Auth0 of similar services has constant issues with it. https://github.com/cypress-io/cypress/commits/feature-multidomain -> it seems like there is not much progress so far, only fixes and merges... |
The amount of AaaS providers that are recommending people move to additional tools instead of Cypress due to this are growing fast. |
What is AaaS? |
Going to guess, Automation as a Service? |
Question! Is there any way we can already start using it partially? For example, there's a ticket “Remove need for hard-coded domain”, but actually I'd be happy to configure a list of hard-coded domains that I use, there's no need for cypress to detect anything automatically for my use case. So basically, if something is already working partially, is it possible to start using it? And if not, any chance to have a half-baked solution that works? |
Still waiting and hoping of multidomain support =^_^= |
This work is still in progress. We have an extremely basic working example that will not currently work in the majority of cases because there's still a lot of work to be done. Regarding the "Remove need for hard-coded domain" - the branch was made to work for an exact hard-coded 127.0.0.1 domain to switch to another domain, so this does not mean that any domain could be hard coded to work. Anyone is welcome to pull down the branch and work with it. This is open source, but I doubt there will be much value in it in its current state. This is our highest priority work alongside WebKit support, so it is a core focus of ours. We hope to parallelize the work soon as we make progress on some core work necessary to unblock that. |
Authorization as a Service fits the context here better in my opinion - Auth0, Okta, etc |
@AndreyYevtukhov are you currently using the Cypress Auth0 authorization patterns for navigating this? Can you share more about your experience? |
Any tips for approach for doing tests for something like a content management system. Create and publish a page on one url and then view the end result on another? |
Auth0 does not have an API to authenticate users from organizations... (https://auth0.com/docs/organizations) That's why we have to authenticate test-users using redirects, UI, requests interception, saving tokens in the files, and reading them before tests... Probably it is not a Cypress issue itself, functionality is missed (or closed) in API from the Auth0 side. Still, it is not possible to open 2 different domains in 1 test (because it is not supported by Cypress) which would make this "flow" much easier and faster... |
Is there any update on this issue? |
The code for this is done in cypress-io/cypress#18075, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
We will close this epic once the feature is generally available. |
The Session and Origin Experiment is be generally available in Cypress 12. Closing as complete. |
This issue is used for tracking work required to provide 'multidomain' support, closing #944
Work being done in https://github.com/cypress-io/cypress/tree/feature-multidomain branch currently.
Some issues covering this work below, but any issue prefixed with "Mult-domain" needs to be delivered.
The text was updated successfully, but these errors were encountered: