Skip to content

Commit 0d5efcf

Browse files
Piotr ZawadzkiPiotr Zawadzki
authored andcommitted
Added "Why use it?" section in README
1 parent 45b0786 commit 0d5efcf

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,13 @@
22

33
This library allows you to run Android UI tests multiple times in a single instrumentation execution. Written in Kotlin.
44

5+
# Why use it?
6+
Let's face it - instrumentation tests can be flaky. Even if your brand new test passes the first time you run it on a device, it doesn't mean that it won't fail if you run it again. Therefore, it's a good practice to try it at least a couple of times just to be sure.
7+
8+
Common approaches are to either run the test over and over again via e.g. consecutive `./gradlew connectedDebugAndroidTest` calls or to copy-paste that test with different names and run the test suite once. Neither one of these is perfect and that's where Android Test XRunner comes into play.
9+
10+
It heavily depends on [Android Test Orchestrator](https://medium.com/stepstone-tech/android-test-orchestrator-unmasked-83b8879928fa), which it "tricks" to execute same tests multiple times.
11+
512
# Getting started
613

714
## Setup

0 commit comments

Comments
 (0)