Automattic / Automattic/simplenote-android

Fix instrumented tests

Open
#1,744 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Java
Stars
1.9k
Forks
318
Avg merge
15h 23m
Merged PRs (30d)
5

Description

Comes from https://github.com/Automattic/simplenote-android/pull/1733/files#r2253935365

> 2. Warning (⚠️): In addition to having unit test working, let's consider having instrumented tests working as well, in this or another follow-up PR (if not too much of a trouble). On that side of things I have the following:
> 1. First, we need to add this `androidTestImplementation 'androidx.test.uiautomator:uiautomator:2.3.0'` dependency to have those instrumented tests compile.
> 2. Then, we need to use `./gradlew Simplenote:connectedDebugAndroidTest` over `./gradlew connectedDebugAndroidTest` to make them run, because otherwise compilation fails on the `PasscodeLock` module with multiple duplicate class failures on Kotlin (we might consider getting to the bottom of this).
> 3. Finally, after managing to run instrumented tests successfully, you'll find that at least `13/74` fail.

Contributor guide

Open the contributing guide

Research direction

Start with the instrumented-test setup referenced in the pull request discussion and the PasscodeLock module. Add the stated UI Automator test dependency, run ./gradlew Simplenote:connectedDebugAndroidTest, and inspect the 13 failing tests among the 74 reported. Done means the instrumented tests compile and run without duplicate-class failures, with the identified failures resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java, kotlin
Domain
build-system, mobile-dev, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.