android / android/nowinandroid
[FR]: Rewrite UI tests to take advantage of Robot design pattern
- Dominant language
- Kotlin
- Stars
- 21.8k
- Forks
- 4.6k
- Avg merge
- 19h 20m
- Merged PRs (30d)
- 2
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the problem
Designed by Jake Wharton, Robot pattern makes for both much more readable UI tests and much easier code reusability.
Quick description of the pattern in conjunction with compose: https://proandroiddev.com/lessons-learned-on-jetpack-compose-ui-testing-robot-pattern-d5e82a9f4efc
### Describe the solution
I've rewritten all feature UI tests with this pattern.
### Additional context
I know it's a lot of changes, but I really wanted to contribute and I thought it would be better to do everything in one fell swoop to keep consistency between all tests. There are no actual logic changes in tests themselves, except for one which I mentioned in the PR.
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
No files or test paths are named in the issue. Start by locating the feature UI tests and read the linked Robot-pattern article; done means the UI tests consistently use the Robot pattern while preserving their existing logic, apart from the one change noted in the pull request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100