zec
/
secant-android-wallet
mirror of https://github.com/zcash/secant-android-wallet.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[#705] Instrumentation coverage generation fails locally

This commit is contained in:
Honza Rychnovsky 2023-03-31 18:47:57 +02:00 committed by GitHub
parent 5296dc5ea9
commit 859ec1591e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/testing/Testing.md
View File

@ -7,9 +7,6 @@ This documentation outlines our approach to testing. By running tests against ou
<!-- TODO [#682]: Testing documentation update --> <!-- TODO [#682]: Testing documentation update -->
<!-- TODO [#682]: https://github.com/zcash/secant-android-wallet/issues/682 --> <!-- TODO [#682]: https://github.com/zcash/secant-android-wallet/issues/682 -->
<!-- TODO [#705] Instrumentation coverage generation fails when run locally -->
<!-- TODO [#705] https://github.com/zcash/secant-android-wallet/issues/705-->
## Manual testing ## Manual testing
We aim to automate as much as we possibly can. Still manual testing is really important for Quality Assurance. We aim to automate as much as we possibly can. Still manual testing is really important for Quality Assurance.
@ -28,7 +25,7 @@ The Android Gradle plugin supports code coverage with Jacoco. This integration
When coverage is enabled, running instrumentation tests will automatically generate coverage reports stored under `$module/build/reports/coverage`. When coverage is enabled, running instrumentation tests will automatically generate coverage reports stored under `$module/build/reports/coverage`.
### Generating code coverage locally ### Generating code coverage locally
- `./gradlew <android-module-name>:connectedCheck -PIS_ANDROID_INSTRUMENTATION_TEST_COVERAGE_ENABLED=true` for Android modules. These modules internally use JaCoCo to generate test coverage. - `./gradlew <android-module-name>:connectedCheck -PIS_ANDROID_INSTRUMENTATION_TEST_COVERAGE_ENABLED=true` for Android modules. These modules internally use JaCoCo to generate test coverage. You can then find the coverage report in `<android-module-name>/build/reports/coverage/androidTest/debug/connected/index.html`.
- `./gradlew <kotlin-only-module-name>:check` for Kotlin modules. These modules internally use Kover to generate test coverage. You can then find the coverage report in `<kotlin-only-module-name>/build/kover/html/index.html`. - `./gradlew <kotlin-only-module-name>:check` for Kotlin modules. These modules internally use Kover to generate test coverage. You can then find the coverage report in `<kotlin-only-module-name>/build/kover/html/index.html`.
### Generating code coverage with emulator.wtf ### Generating code coverage with emulator.wtf