mirror of
https://github.com/vector-im/element-android.git
synced 2024-11-15 01:35:07 +08:00
88 lines
3.1 KiB
Markdown
88 lines
3.1 KiB
Markdown
|
# Automate user interface tests
|
||
|
|
|
||
|
|
Element Android ensures that some fundamental flows are properly working by running automated user interface tests.
|
||
|
|
Ui tests are using the android [Espresso](https://developer.android.com/training/testing/espresso) library.
|
||
|
|
|
||
|
|
Tests can be run on a real device, or on a virtual device (such as the emulator in Android Studio).
|
||
|
|
|
||
|
|
Currently the test are covering a small set of application flows:
|
||
|
|
- Registration
|
||
|
|
- Self verification via emoji
|
||
|
|
- Self verification via passphrase
|
||
|
|
|
||
|
|
## Prerequisites:
|
||
|
|
|
||
|
|
Out of the box, the tests use one of the homeservers (located at http://localhost:8080) of the "Demo Federation of Homeservers" (https://github.com/matrix-org/synapse#running-a-demo-federation-of-synapses).
|
||
|
|
|
||
|
|
You first need to follow instructions to set up Synapse in development mode at https://github.com/matrix-org/synapse#synapse-development. If you have already installed all dependencies, the steps are:
|
||
|
|
|
||
|
|
```
|
||
|
|
$ git clone https://github.com/matrix-org/synapse.git
|
||
|
|
$ cd synapse
|
||
|
|
$ virtualenv -p python3 env
|
||
|
|
$ source env/bin/activate
|
||
|
|
(env) $ python -m pip install --no-use-pep517 -e .`
|
||
|
|
```
|
||
|
|
|
||
|
|
Every time you want to launch these test homeservers, type:
|
||
|
|
|
||
|
|
```
|
||
|
|
$ virtualenv -p python3 env
|
||
|
|
$ source env/bin/activate
|
||
|
|
(env) $ demo/start.sh --no-rate-limit`
|
||
|
|
```
|
||
|
|
|
||
|
|
**Emulator/Device set up**
|
||
|
|
|
||
|
|
When running the test via android studio on a device, you have to disable system animations in order for the test to work properly.
|
||
|
|
|
||
|
|
First, ensure developer mode is enabled:
|
||
|
|
|
||
|
|
- To enable developer options, tap the **Build Number** option 7 times. You can find this option in one of the following locations, depending on your Android version:
|
||
|
|
|
||
|
|
- Android 9 (API level 28) and higher: **Settings > About Phone > Build Number**
|
||
|
|
- Android 8.0.0 (API level 26) and Android 8.1.0 (API level 26): **Settings > System > About Phone > Build Number**
|
||
|
|
- Android 7.1 (API level 25) and lower: **Settings > About Phone > Build Number**
|
||
|
|
|
||
|
|
On your device, under **Settings > Developer options**, disable the following 3 settings:
|
||
|
|
|
||
|
|
- Window animation scale
|
||
|
|
- Transition animation scale
|
||
|
|
- Animator duration scale
|
||
|
|
|
||
|
|
|
||
|
|
## Recipes
|
||
|
|
|
||
|
|
We added some specific Espresso IdlingResources, and other utilities for matrix related tests
|
||
|
|
|
||
|
|
### Wait for initial sync
|
||
|
|
|
||
|
|
````
|
||
|
|
// Wait for initial sync and check room list is there
|
||
|
|
withIdlingResource(initialSyncIdlingResource(uiSession)) {
|
||
|
|
onView(withId(R.id.roomListContainer))
|
||
|
|
.check(matches(isDisplayed()))
|
||
|
|
}
|
||
|
|
````
|
||
|
|
|
||
|
|
### Accessing current activity
|
||
|
|
|
||
|
|
````
|
||
|
|
val activity = EspressoHelper.getCurrentActivity()!!
|
||
|
|
val uiSession = (activity as HomeActivity).activeSessionHolder.getActiveSession()
|
||
|
|
````
|
||
|
|
|
||
|
|
### Interact with other session
|
||
|
|
|
||
|
|
It's possible to create a session via the SDK, and then use this session to interact with the one that the emulator is using (to check verifications for example)
|
||
|
|
|
||
|
|
````
|
||
|
|
@Before
|
||
|
|
fun initAccount() {
|
||
|
|
val context = InstrumentationRegistry.getInstrumentation().targetContext
|
||
|
|
val matrix = Matrix.getInstance(context)
|
||
|
|
val userName = "foobar_${System.currentTimeMillis()}"
|
||
|
|
existingSession = createAccountAndSync(matrix, userName, password, true)
|
||
|
|
}
|
||
|
|
`````
|