Bump test coverage to 60%

Description

Contributor guide

Tech stack

javaandroid

Domain

mobiletesting

Issue type

test

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

unclear

Prerequisites

JavaAndroid developmentUnit testingCode coverage tools

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

25

Research direction

First, examine the project's build.gradle for test coverage configuration (like Jacoco). Then, run the existing tests to see current coverage. Identify files with low coverage using a coverage report. Write unit tests for those files following the patterns of existing tests. Ensure the coverage threshold of 60% is met overall.