-
Notifications
You must be signed in to change notification settings - Fork 18
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
Support for XCUITest ? #2
Comments
Hey, yes, this will work for any kind of tests since it globally swaps out url handling with its own implementation. Just call |
I tried & it doesn't seems to be working.. Do you have any example that worked for UI tests ? Do we need to do specific configuration in order to get that working. I will probably create demo project and send it to you as an example. |
Interesting… I never tried it with UI tests, a quick sample project would be helpful. But now that I think about it some more it indeed might be an issue because the ui tests launch the app differently. So maybe passing launch arguments and then doing something in the application target to stub might be needed. Not ideal. If you can provide a sample great, I'll further investigate too later today |
Yes UI Tests are designed as black box and there is no access to app code directly. The Swifter framework works with UI Tests but shame its not updated for Swift 4. It launch web server in the UI test process itself on |
Interesting approach that – for those cases we've used a separate small web app written in Sinatra but embedding is pretty clever. Somehow Swifter flew under my radar |
This is quick question not an issue.
DO you think this approach will wok to stub the Xcode UI Tests as well ?
@JanGorman Let me know what you think ?
The text was updated successfully, but these errors were encountered: