I made a test project with both Cucumber and plain Espresso tests, using a custom runner extending CucumberAndroidJUnitRunner.
I tested it with files in Kotlin and worked.
I tested it again with files in Java and, when I try to run my plain Espresso test, my Cucumber test is launched instead, every single time.
β What did you expect to see?
I expected that both Cucumber and plain Espresso tests would work in Java, same as in Kotlin.
Reproduce it using this test project.
Last commit in main branch is in Java and failing, if you just checkout previous commit it is in Kotlin and both tests work.
Steps to reproduce the behavior:
Open project
Run test MainActivitySteps and verify it's passing
Run test ExampleInstrumentedTest and verify MainActivitySteps is running instead
Checkout commit "both tests working in Kotlin" 48735819
Run test MainActivitySteps and verify it's passing
Run test ExampleInstrumentedTest and verify it actually runs and passes
π What did you see?
I made a test project with both Cucumber and plain Espresso tests, using a custom runner extending CucumberAndroidJUnitRunner. I tested it with files in Kotlin and worked. I tested it again with files in Java and, when I try to run my plain Espresso test, my Cucumber test is launched instead, every single time.
β What did you expect to see?
I expected that both Cucumber and plain Espresso tests would work in Java, same as in Kotlin.
π¦ Which tool/library version are you using?
π¬ How could we reproduce it?
Reproduce it using this test project. Last commit in main branch is in Java and failing, if you just checkout previous commit it is in Kotlin and both tests work.
Steps to reproduce the behavior:
π Any additional context?
This text was originally generated from a template, then edited by hand. You can modify the template here.