Skip to content
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

EarlGrey v2 update #946

Closed
bootstraponline opened this issue Sep 24, 2018 · 4 comments
Closed

EarlGrey v2 update #946

bootstraponline opened this issue Sep 24, 2018 · 4 comments

Comments

@bootstraponline
Copy link

EarlGrey v2 has been released. https://github.com/google/EarlGrey/tree/earlgrey2

Opening this issue to track progress on migrating.

@LeoNatan
Copy link
Contributor

Thanks for letting us know.

I'm not sure how easy or desireable this transition will be. Reading https://github.com/google/EarlGrey/tree/earlgrey2#caveats, that's a problem. Right now we do not use test targets, we just embed the EarlGrey usage inside during app launch. This requires a completely different setup.

@LeoNatan
Copy link
Contributor

LeoNatan commented Oct 1, 2019

We are investigating new ways to advance the project. EGv2 seems unlikely at this point. Closing.

@LeoNatan LeoNatan closed this as completed Oct 1, 2019
@bootstraponline
Copy link
Author

I'm curious what alternatives you're investigating? XCUITest?

@LeoNatan
Copy link
Contributor

LeoNatan commented Oct 1, 2019

The plan is to use XCUITest for matchers and actions, while using DetoxSync for synchronizing efficiently. EG's runloop spinning (busy wait) is killing our performance profiling aspirations, so we just can't rely on it anymore.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants