EarlGrey 1.0 > EarlGrey 2.0 (UI automation test framework)
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 251
- Forks
- 142
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 3
Description
More information:
https://opensource.google.com/projects/earlgrey
Git branch for EarlGrey 2.0:
https://github.com/google/EarlGrey/tree/earlgrey2
Using EarlGrey 2.0:
https://github.com/google/EarlGrey/blob/earlgrey2/docs/setup.md#using-earlgrey-20
Might also help with automated screenshot generation. (https://github.com/owncloud/ios-app/issues/324#issuecomment-477904155)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked EarlGrey 2.0 branch and its docs/setup.md first, then compare the app's existing EarlGrey 1.0 test setup. Identify the tests and configuration affected by the migration; done means the iOS test suite uses EarlGrey 2.0, with automated screenshot generation considered separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100