apache / apache/cordova-android
Automate `gradle connectedAndroidTests`
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.6k
- Avg merge
- 16h 18m
- Merged PRs (30d)
- 11
Description
This project has additional tests to the normal JS stuff in https://github.com/apache/cordova-android/tree/master/test. Two commands: `gradlew test` (unit tests) and `gradlew connectedAndroidTest` (instrumentation tests).
The unit tests are part of the CI run via https://github.com/apache/cordova-android/blob/master/test/run_java_unit_tests.js:
https://github.com/apache/cordova-android/blob/ef2434188efeef868e91232188ef080acdd28e32/package.json#L21-L30
But I couldn't find anything for the `connectedAndroidTest`, which probably means this test is not run automatically right now.
(Both test types pass right now by the way.)
Contributor guide
Research direction
Start with test/run_java_unit_tests.js and the referenced package.json scripts to understand how unit tests enter CI. Run gradlew test and gradlew connectedAndroidTest locally, then trace the existing CI test setup. Done means connectedAndroidTest runs automatically as part of CI alongside the unit tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript
- Domain
- ci-cd, mobile, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100