android / android/android-test
Feature Request: Allow for adding comments to AndroidJUnitRunner flat test file execution option
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 342
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 2
Description
Currently, we (Mozilla) have large `androidTest` (Espresso) test suites with a lot of annotated disabled tests for `@Ignore` (using `org.junit.Ignore`). The default `@Ignore` JUnit Annotation allows for a default parameter of which we make use for linking back to issue trackers (e.g, `@Ignore("Blocked on X")`
I've been looking at the AndroidJUnitRunner documentation for exploring alternative ways to handle manifests (e.g, maintaining a remote list of disabled tests that can be updated in one spot), alongside the execution option `notTestFile` for listing tests we want disabled without having to annotate.
One aspect missing from a flat test manifest file is the ability to give context to the listing such as adding a comment. Wondering if this can be considered for the future for AndroidJUnitRunner (I'm all ears on other ideas too).
Example: `disabled-tests.txt`
```Text
org.mozilla.fenix.ui.SettingsTests # Rewrite needed to support Compose UI
```
Contributor guide
Research direction
Review the AndroidJUnitRunner documentation and the notTestFile execution option first. Use the disabled-tests.txt example as the acceptance case: entries should support trailing comments such as "# Rewrite needed to support Compose UI" while preserving test selection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100