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
{{ message }}
This repository has been archived by the owner on Aug 7, 2019. It is now read-only.
@tigbro I am trying to test a chrome extension, so changing it's url may not work with this method. That is why I have started to put a chrome extension together to do this. Can you tell me why the iframe must be on the same domain?
However, for building chrome extensions, your browser will be chrome, so you can use the following feature of chrome during testing: start it with the flag --disable-web-security and the same origin policy is deactivated.
And yes, you are right: #22 will remove the need of parent.uitest.instrument.
Tobias
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Here is a first working version: https://github.com/tigbro/uitest-proxy
Needs tests, project build using grunt, standalone start command as well as library export to use it as a connect middleware.
The text was updated successfully, but these errors were encountered: