Hey Joe, EarlGrey right now is based on XCTest. However, the next version being worked on right now should integrate EarlGrey with XCUITest. Do feel free to contribute.
Hi Mathew, EarlGrey already has some support for UIWebView / WKWebView used in hybrid apps. If you meant something else, i'd follow up with them on https://github.com/google/EarlGrey
Hello, I was unable to test WkWebview based Hybrid iOS application using EarlGrey. Can't seem to find a way to test the UI elements in a html which is loaded in my WkWebview. Is there a solution?
While this is a longer discussion, in a nutshell, this is the main advantage to using EarlGrey:
EarlGrey is a grey-box framework rather and a black box framework like XCUITest. You have access to the app's state and the app's variables which makes EarlGrey more versatile. You can create custom matchers, actions and assertions that can utilize all these features to provide a wider coverage.
Please feel free to message us on our Google Group to have a more in-depth discussion.
This is exciting! Is it built on Xcode's existing UI Testing framework or XCTest?
ReplyDeleteHey Joe,
DeleteEarlGrey right now is based on XCTest. However, the next version being worked on right now should integrate EarlGrey with XCUITest. Do feel free to contribute.
Hi Joe,
ReplyDeletethis is built on XCTest. Read more here : https://github.com/google/EarlGrey/blob/master/README.md
Thanks!
Will Earl Grey be able to handle mobile Web Automation?
ReplyDeleteHi Mathew, EarlGrey already has some support for UIWebView / WKWebView used in hybrid apps. If you meant something else, i'd follow up with them on https://github.com/google/EarlGrey
DeleteHello,
DeleteI was unable to test WkWebview based Hybrid iOS application using EarlGrey.
Can't seem to find a way to test the UI elements in a html which is loaded in my WkWebview.
Is there a solution?
why should I chose EarlGrey instead of xcode UI test framework? What are the difference between them?
ReplyDeletegood question. no one reply?
DeleteIndeed!
DeleteWhile this is a longer discussion, in a nutshell, this is the main advantage to using EarlGrey:
DeleteEarlGrey is a grey-box framework rather and a black box framework like XCUITest. You have access to the app's state and the app's variables which makes EarlGrey more versatile. You can create custom matchers, actions and assertions that can utilize all these features to provide a wider coverage.
Please feel free to message us on our Google Group to have a more in-depth discussion.