|
5 | 5 | Gradle custom plugin to setup android test devices. |
6 | 6 |
|
7 | 7 | # Problem |
8 | | -When running Espresso tests for your Android projects on real devices you need to setup these before the tests. Doing this manually takes time and is cumbersome. |
| 8 | +When running Espresso tests for your Android projects on real devices you need to setup these before the tests run. Doing this manually takes time and is cumbersome. |
9 | 9 |
|
10 | 10 | # Solution |
11 | | -Testdevicemanager - It is a custom gradle plugin written in Kotlin. It uses ```adb commands``` to get and set device information. Therefore no additional access rights for connected mobile devices are required. |
| 11 | +Testdevicemanager - It is a custom gradle plugin written in Kotlin. It uses ```adb commands``` to get and set device information. This way, no additional access rights for connected mobile devices are required. |
12 | 12 |
|
13 | 13 | # Features |
14 | | -The following things can be managed by the plugin: |
| 14 | +The following things are handled by the plugin: |
15 | 15 |
|
16 | | -- Locking / Unlocking the device - The device can be unlocked via pressing the power button, swiping, entering a pin or a password |
| 16 | +- Locking / Unlocking the device - The device will be unlocked by pressing the power button, swiping, entering a pin or a password |
17 | 17 |
|
18 | | -- Enabling / Disabling animations - To make sure espresso ui tests run smoothly, animations can be deactivated in the developer options of the test device |
| 18 | +- Enabling / Disabling animations - To make sure espresso ui tests run smoothly, animations will be deactivated in the developer options of the test device |
19 | 19 |
|
20 | | -- Enabling / Disabling the stay awake mode - The device's stay awake mode can be activated in the developer options of the test device, to make sure that the test device does not switch of the screen during testing |
| 20 | +- Enabling / Disabling the stay awake mode - The device's stay awake mode will be activated in the developer options of the test device, to make sure that the test device does not switch of the screen during testing |
21 | 21 |
|
22 | | -- Checking for connection to a specific WLAN - A check for a connection to a specific WLAN can be done |
| 22 | +- Checking for connection to a specific WLAN - A check for a connection to a specific WLAN will be performed |
23 | 23 |
|
24 | 24 | # Integration into the project |
25 | 25 | ## Groovy |
@@ -67,7 +67,7 @@ buildscript { |
67 | 67 | apply(plugin = "de.welt.apps.testdevicemanager") |
68 | 68 | ``` |
69 | 69 | # Setup |
70 | | -All of the following extension values can be maintained but do not need to be used at all. |
| 70 | +All of the following extension values can be used but do not need to be used at all. |
71 | 71 | ``` |
72 | 72 | testDeviceManager { |
73 | 73 | unlockBy = "power button | swipe | pin | password" |
|
0 commit comments