cucumber-android
cucumber-android copied to clipboard
cucumber
Android support for Cucumber-JVM
Steps: 1. Setup Android project with cucumber android - create **several** tests 2. Enable Android Test Orchestrator + set clear package data after each test to true (I followed setup...
### 👓 What did you see? Setting up a new test set resulted in all of the tests to fail. They don't actually run. The cause turned to be a...
### 👓 What did you see? ```` java.lang.IllegalStateException: Test not setup properly. Use a ComposeTestRule in your test to be able to interact with composables at androidx.compose.ui.test.junit4.ComposeRootRegistry_androidKt.ensureComposeRootRegistryIsSetUp(ComposeRootRegistry.android.kt:254) at androidx.compose.ui.test.junit4.ComposeRootRegistry_androidKt.waitForComposeRoots(ComposeRootRegistry.android.kt:261) at...
### 👓 What did you see? no cucumber reports on crashed testcase ### ✅ What did you expect to see? Testcase being marked "failed" ### 📦 Which tool/library version are...
My problem is that when I use **CucumberAndroidJUnitRunner** I'm not able to run the Android instrumented tests and the cucumber ones, only the cucumber tests are running. Even with **CukeulatorAndroidJUnitRunner**....
### 👓 What did you see? When enabling code coverage, it fails to generate a code coverage report and fails the build ### ✅ What did you expect to see?...
Do we have a mechanism to rerun the failed tests 'n' times. As I can see the re-run by file mechanism cannot be implemented since I can see a comment...
This is the first option to resolve https://github.com/cucumber/cucumber-android/issues/32
I'd love to have a mechanism that retries failed tests but not with the rerun file mechanism. I'm interested to have a report that is OK if at least one...
Problem: I am running Cucumber UI tests with Firebase Testlab. All are working fine. The sequential run is successful and getting all reports. Currently, I am trying to distribute the...