From 859ec1591efef551cc191e0467586b3d170400ec Mon Sep 17 00:00:00 2001 From: Honza Rychnovsky Date: Fri, 31 Mar 2023 18:47:57 +0200 Subject: [PATCH] [#705] Instrumentation coverage generation fails locally --- docs/testing/Testing.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/testing/Testing.md b/docs/testing/Testing.md index da951f49..13967fb9 100644 --- a/docs/testing/Testing.md +++ b/docs/testing/Testing.md @@ -7,9 +7,6 @@ This documentation outlines our approach to testing. By running tests against ou - - - ## Manual testing 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`. ### Generating code coverage locally -- `./gradlew :connectedCheck -PIS_ANDROID_INSTRUMENTATION_TEST_COVERAGE_ENABLED=true` for Android modules. These modules internally use JaCoCo to generate test coverage. +- `./gradlew :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 `/build/reports/coverage/androidTest/debug/connected/index.html`. - `./gradlew :check` for Kotlin modules. These modules internally use Kover to generate test coverage. You can then find the coverage report in `/build/kover/html/index.html`. ### Generating code coverage with emulator.wtf