Skip to content

Working with Android OS. Kaspresso Device abstraction.

Device is a provider of managers for all off-screen work.

Structure

All examples are located in device_tests. Device provides these managers:

  1. apps allows to install or uninstall applications. Uses adb install and adb uninstall commands. See the example DeviceAppSampleTest.
  2. activities is an interface to work with currently resumed Activities. AdbServer not required. See the example DeviceActivitiesSampleTest.
  3. files provides the possibility of pushing or removing files from the device. Uses adb push and adb rm commands and does not require android.permission.WRITE_EXTERNAL_STORAGE permission. See the example DeviceFilesSampleTest.
  4. internet allows toggling WiFi and network data transfer settings. Be careful of using this interface, WiFi settings changes could not work with some Android versions. See the example DeviceNetworkSampleTest.
  5. keyboard is an interface to send key events via adb. Use it only when Espresso or UiAutomator are not appropriate (e.g. screen is locked). See the example DeviceKeyboardSampleTest.
  6. location emulates fake location and allows to toggle GPS setting. See the example DeviceLocationSampleTest.
  7. phone allows to emulate incoming calls and receive SMS messages. Works only on emulators since uses adb emu commands. See the example DevicePhoneSampleTest.
  8. screenshots is an interface screenshots of currently resumed activity. Requires android.permission.WRITE_EXTERNAL_STORAGE permission. See the example DeviceScreenshotSampleTest.
  9. accessibility allows to enable or disable accessibility services. Available since api 24. See the example DeviceAccessibilitySampleTest.
  10. permissions provides the possibility of allowing or denying permission requests via default Android permission dialog. See the example DevicePermissionsSampleTest.
  11. hackPermissions provides the possibility of allowing any permission requests without default Android permission dialog. See the example DeviceHackPermissionsSampleTest.
  12. exploit allows to rotate device or press system buttons. See the example DeviceExploitSampleTest.
  13. language allows to switch language. See the example DeviceLanguageSampleTest.
  14. logcat provides access to adb logcat. See the example DeviceLogcatSampleTest.
    The purpose of logcat:
    If you have not heard about GDPR and high-profile lawsuits then you are lucky. But, if your application works in Europe then it's so important to enable/disable all analytics/statistics according to acceptance of the agreements. One of the most reliable ways to check analytics/statistics sending is to verify logcat where all analytics/statistics write their logs (in debug mode, sure). That's why we have created a special Logcat class providing a wide variety of ways to check logcat.
  15. uiDevice returns an instance of android.support.test.uiautomator.UiDevice. We don't recommend to use it directly because there is Kautomator that offers a more readable, predictable and stable API to work outside your application.

Also Device provides application and test contexts - targetContext and context.

Usage

Device instance is available in BaseTestContext scope and BaseTestCase via device property. 

@Test
fun test() =
    run {
        step("Open Simple Screen") {
            activityTestRule.launchActivity(null)
  ======>   device.screenshots.take("Additional_screenshot")  <======

            MainScreen {
                simpleButton {
                    isVisible()
                    click()
                }
            }
        }
        // ....
}

Restrictions

Most of the features that Device provides use of adb commands and requires AdbServer to be run. Some of them, such as call emulation or SMS receiving, could be executed only on emulator. All such methods are marked by annotation @RequiresAdbServer.

All the methods which use ADB commands require android.permission.INTERNET permission. For more information, see AdbServer documentation.