Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move all Android Unit Tests to Junit 4

Open
  • Is something wrong?
#9,134 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #9260 by @one-kash — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, kotlin
Domain
mobile-dev, testing-qa

Research direction

Start by locating the Android unit tests and their test-runner configuration. Check how they run on API 21–25 and identify which tests still need to move to JUnit 4. Done means all Android unit tests use JUnit 4 and run on those API versions.

Written by the indexing model from the issue text.

Description

enhancement

As a minimum, use Junit 4 for Android Unit Tests

They aren't running on API 21-25 anymore

Dominant language
Kotlin
Stars
47.1k
Forks
9.3k
Avg merge
2d 15h
Merged PRs (30d)
21

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lysine-dev/okhttp

All issues in lysine-dev/okhttp

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.