v1.1.0 (Feb 11, 2020)
Sep 12, 2019
Mar 12, 2020
Kaspersky Lab (KasperskyLab)
Dmitriy Voronin (dsvoronin)
Nikolay Nesterov (nesterov-n)
Alexander Blinov (xanderblinov)
Pavel Strelchenko (PStrelchenko)
Artur Artikov (aartikov)
Eugene Matsyuk (matzuk)
Egor Kurnikov (eakurnikov)
Andrey Antipov (AntipovAndrey)
Ruslan Mingaliev (RuslanMingaliev)
Dmitriy Movchan (v1sar)
Alexey Demov (avesha)
Vyacheslav Rodionov (v-rodionov)
Amit Barjatya (AmitBarjatya)
Andrey Beryukhov (AndreySBer)
Show all (20)20
Source code
APK file



Kaspresso is a great UiTest framework based on Espresso and UI Automator, and providing a wide set of such amazing features as:

  1. 100% stability.
  2. Increased speed of Espresso and UiAutomator command execution. In case of UiAutomator, we get 10x acceleration for some commands!

  3. Beautiful readability through human DSL.
  4. Incredible mechanism of interceptors allowing you to catch all action and assertions in one place!
  5. Understandable and full logging.
  6. Ability to call ADB commands.
  7. Philosophy how to write ui-tests and DSL providing this philosophy.
  8. Light and convenient feature's screenshoting.
  9. Etc.

Dive deep into capabilities of Kaspresso!



We like a syntax to write ui-tests providing by Kakao (a wrapper over Espresso offering Kotlin DSL approach). Just compare.


fun testFirstFeature() {


fun testFirstFeature() {
    mainScreen {
        toFirstFeatureButton {

In according to this approach, we decided to write the same wrapper over UI Automator and called it Kautomator. Have a look at the code below. UiAutomator:

val instrumentation: Instrumentation = InstrumentationRegistry.getInstrumentation()
val uiDevice = UiDevice.getInstance(instrumentation)

val uiObject = uiDevice.wait(

uiObject.text = "Kaspresso"
assertEquals(uiObject.text, "Kaspresso")


MainScreen {
    simpleEditText {

As we mentioned Kakao and Kautomator offer almost identical API to work. So, a developer doesn't feel the difference while they write a test and use Espresso or UiAutomator under the hood. Please, read about Kakao and Kautomator in details.

But, the existance of only suitable Kotlin DSL wrappers over libraries doesn't help to correlate your test with the test-case on which this test is based. Also, the long test often transforms into an inseparable code wall. It's a problem. That's why we have created an additional Kotlin DSL allowing you to make the perception of your test at absolutely another level.

Please, observe the code below:

fun shouldPassOnNoInternetScanTest() =
    beforeTest {
        // some things with the state
    }.afterTest {
        // some things with the state
    }.run {
        step("Open Simple Screen") {
            MainScreen {
                nextButton {

        step("Click button_1 and check button_2") {
            SimpleScreen {
                button1 {
                button2 {

        step("Click button_2 and check edit") {
            SimpleScreen {
                button2 {
                edit {
                    flakySafely(timeoutMs = 7000) { isVisible() }

        step("Check all possibilities of edit") {

A great manual about how to write tests correctly is availbable here.


Flakiness in UI tests means that one test can pass 10 times in a row, but breaks on the eleventh attempt. The reason for failure is so mysterious and unpredictable, and all of this magic sometimes forces you to cry when nobody sees you. Unfortunately, the most popular reason for such behavior is the instability of ui-tests libraries (Espresso and UI Automator). More detailed info about interceptors is here and here. Also, some sweet features helping to resolve a lot of typical problems are available in Kaspresso.Kaspresso eliminates instability of ui-tests libraries thanks to DSL wrappers and the new mechanism of interceptors where all failures are caught.

UI-test libraries acceleration

Shut up and watch the video =)

The left video is a boosted UI Automator, the right video is a default UI Automator.

How is it possible? Please, review the short explanation.


We have introduced a mechanism of interceptors giving an ability to catch all actions going to Espresso or UI Automator. Thanks to this mechanism, a developer can add additional custom actions to each library operation (a logging, a screenshot), try to overcome flaky library operations (re-run failed actions, scroll the parent layout, remove the android system dialog) and do other interesting things. Please, read the comprehensive manual.


Kaspresso transform your tests' logs into understandable and pleasant text:

Ability to call Adb commands

Espresso and UI Automator don't allow to call adb commands inside a test. That's why we have written special AdbServer repository fixing mentioned problem.

In Kaspresso, the developer can call ADB and CMD commands by AdbServer class. The manual is here

Ability to work with Android System

There are a lot of useful classes in Kaspresso to work with Android System.

Examples of such work: 1. push/pull files, 2. enable/disable network, 3. give permissions like a user does, 4. emulate phone calls, 5. make screenshots, 6. enable/disable gps, 7. set geo location, 8. enable/disable accessibility, 9. change app language, 10. collect and parse logcat, 11. etc.

A developer can use all of this through Device class.

Feature's screenshotting

If you develop an application that is available across the world then you have to support a lot of localizations. Translation of a word or a phrase is not a big challenge. But, the most important task is to translate according to context of a specific screen and language culture. That's why a translator must not only have the set of new words/phrases but, also, a set of screens where these words/phrases are used. Kaspresso offers a possibility to make screenshots fast and automatically. Also, we prepared a comprehensive manual and an example of how to make screenshots even for legacy screens almost immediately. The spoiler: you don't have to refactor or to mock all of this =)


We give broad opportunities to tune any part of Kaspresso. Read info and enjoy it =)

The philosophy

The suitable tool to write UI-tests is a necessary requirement but this tool doesn't resolve all problems. Another big bunch of questions is how to write tests and how to organize the entire process. Our team has great experience in introducing autotests in different companies. That's why we have prepared a lot of articles which are devoted to these problems. Welcome to learn our lessons =)


For all information check Kaspresso wiki


Include the jcenter repository to your root build.gradle file (if it does not exist already):

allprojects {
    repositories {

And then add dependency to your module build.gradle:

androidTestImplementation 'com.kaspersky.android-components:kaspresso:1.1.0'

If you are still using old Android Support libraries we strongly recommend to migrate to AndroidX. The last version with Android Support libraries is:

androidTestImplementation 'com.kaspersky.android-components:kaspresso:1.0.1-support'


English support in telegram - t.me/kaspresso_en Russian support in telegram - t.me/kaspresso

Contribution Policy

Kaspresso is an open source project, and depends on its users to improve it. We are more than happy to find you interested in taking the project forward. Kindly refer to the Contribution Guidelines for detailed information.


Kaspresso is open source and available under the Apache License, Version 2.0.