Investigate unifying lint and error prone test cases
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by locating the existing lint and Error Prone test cases and compare their coverage and structure. Determine whether they can share a unified set of cases without losing coverage; done means the cases remain in parity and duplicated coverage is removed.
Written by the indexing model from the issue text.
Description
Gives us a lot more coverage and ensures they're kept at parity, as well as avoiding duplication.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 229
- PR merge metrics
- No merged PRs in 30d
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.
More from uber/AutoDispose
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
uber/AutoDispose#501 ·
-
Enhancement Kotlin On Hold
Difficulty 5/5 Over a week Newbie friendliness 20/100
uber/AutoDispose#370 · 4 comments ·
All issues in uber/AutoDispose
Similar issues
-
Bug Java Platform: Java
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/sentry-java#6138 · 1 comment ·
-
bug needs triage p2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
GoogleCloudPlatform/DataflowTemplates#4273 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100