Essential Android Writing UI tests edit forum

Writing UI tests - Android

Versions

[{“Name”:“1.1”,“GroupName”:null}]

Introduction

Focus of this document is to represent goals and ways how to write android UI and integration tests. Espresso and UIAutomator are provided by Google so focus should be around these tools and their respective wrappers e.g. Appium, Spoon etc.

Syntax

Remarks

JUnit rules:

As you can see in MockWebServer example and ActivityTestRule they all fall under category of JUnit rules which you can create yourself which then should be executed for each test defining its behaviour @see: https://github.com/junit-team/junit4/wiki/rules

Appium

Parameters

Since parameters have some issues placing them here until documentation bug is resolved:

Parameter | Details | —— | —— | Class activityClass | which activity to start | initialTouchMode | should the activity be placed in touch mode on start: https://android-developers.blogspot.de/2008/12/touch-mode.html | launchActivity | true if the Activity should be launched once per Test method. It will be launched before the first Before method, and terminated after the last After method. |


Table Of Contents
39 ACRA
64 Menu
94 Writing UI tests
112 Loader
119 Xposed
132 Colors
135 Fresco
140 AdMob
147 Button
156 Vk SDK
170 XMPP
176 OpenCV
200 FileIO
203 Moshi
217 Paint
231 AIDL
241 JCodec
243 Okio
255 Looper
  ↑ ↓ to navigate     ↵ to select     Esc to close