Closed mandrachek closed 1 year ago
Adding:
<instrumentation
android:name="io.qameta.allure.android.runners.AllureAndroidJUnitRunner"
android:targetPackage="APP_PACKAGE_HERE"/>
To the AndroidManifest.xml seems to have solved this problem.
I'm submitting a ...
What is the current behavior?
Using a test module, and replacing
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
withtestInstrumentationRunner "io.qameta.allure.android.runners.AllureAndroidJUnitRunner"
results in 0 tests found.If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
I have a small application, with a single activity in the typical :app module. I've created a test module as mentioned above, and have set the
targetProjectPath
to:app
. In mytest/src/main/java
, I have a single test class and single test method. The same fordebug/src/main/java
andrelease/src/main/java
(except different class names and sub-packages for debug and release specific tests. TheAndroidJUnitRunner
successfully finds 2 tests (main and debug) when I runconnectedDebugAndroidTest
.What is the expected behavior?
AllureAndroidJUnitRunner
should find and execute the same tests asAndroidJunitRunner
What is the motivation / use case for changing the behavior?
To be able to use allure.
Please tell us about your environment:
| Test framework | junit@4.13.2| | Allure integration | allure-kotlin-android@2.4.0 |
Other information
My test module's build.gradle looks like this: