I&#39;m trying to make UI test for my android app in Kotlin. Since the new system using ActivityTestRule, I can&#39;t make it work: it compiles correctly, and at runtime, I get:

```lang-none
java.lang.Exception: The @Rule &#39;mActivityRule&#39; must be public.
    at org.junit.internal.runners.rules.RuleFieldValidator.addError(RuleFieldValidator.java:90)
    at org.junit.internal.runners.rules.RuleFieldValidator.validatePublic(RuleFieldValidator.java:67)
    at org.junit.internal.runners.rules.RuleFieldValidator.validateField(RuleFieldValidator.java:55)
    at org.junit.internal.runners.rules.RuleFieldValidator.validate(RuleFieldValidator.java:50)
    at org.junit.runners.BlockJUnit4ClassRunner.validateFields(BlockJUnit4ClassRunner.java:170)
    at org.junit.runners.BlockJUnit4ClassRunner.collectInitializationErrors(BlockJUnit4ClassRunner.java:103)
    at org.junit.runners.ParentRunner.validate(ParentRunner.java:344)
    at org.junit.runners.ParentRunner.&lt;init&gt;(ParentRunner.java:74)
    at org.junit.runners.BlockJUnit4ClassRunner.&lt;init&gt;(BlockJUnit4ClassRunner.java:55)
    at android.support.test.internal.runner.junit4.AndroidJUnit4ClassRunner.&lt;init&gt;(AndroidJUnit4ClassRunner.java:38)
    at android.support.test.runner.AndroidJUnit4.&lt;init&gt;(AndroidJUnit4.java:36)
    at java.lang.reflect.Constructor.constructNative(Native Method)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
    at android.support.test.internal.runner.junit4.AndroidAnnotatedBuilder.buildAndroidRunner(AndroidAnnotatedBuilder.java:57)
    at android.support.test.internal.runner.junit4.AndroidAnnotatedBuilder.runnerForClass(AndroidAnnotatedBuilder.java:45)
    at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
    at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
    at org.junit.runner.Computer.getRunner(Computer.java:38)
    at org.junit.runner.Computer$1.runnerForClass(Computer.java:29)
    at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
    at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:98)
    at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:84)
    at org.junit.runners.Suite.&lt;init&gt;(Suite.java:79)
    at org.junit.runner.Computer.getSuite(Computer.java:26)
    at android.support.test.internal.runner.TestRequestBuilder.classes(TestRequestBuilder.java:691)
    at android.support.test.internal.runner.TestRequestBuilder.build(TestRequestBuilder.java:654)
    at android.support.test.runner.AndroidJUnitRunner.buildRequest(AndroidJUnitRunner.java:329)
    at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:226)
    at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1584)
```

Here is how I declared mActivityRule:

    RunWith(javaClass&lt;AndroidJUnit4&gt;())
    LargeTest
    public class RadisTest {
    
        Rule
        public val mActivityRule: ActivityTestRule&lt;MainActivity&gt; = ActivityTestRule(javaClass&lt;MainActivity&gt;())
    
       ...
    }

It is already public :/

Kotlin and new ActivityTestRule : The @Rule must be public

In case of a test that crosses multiple activities, is there a way to get current activity? 

getActivtiy() method just gives one activity that was used to start the test.

I tried something like below,

    public Activity getCurrentActivity() {
		Activity activity = null;
		ActivityManager am = (ActivityManager) this.getActivity().getSystemService(Context.ACTIVITY_SERVICE);
		List&lt;ActivityManager.RunningTaskInfo&gt; taskInfo = am.getRunningTasks(1);
		try {
			Class&lt;?&gt; myClass = taskInfo.get(0).topActivity.getClass();
			activity = (Activity) myClass.newInstance();
		}
		catch (Exception e) {

		}
		return activity;
	}
but I get null object.

Get Current Activity in Espresso android

Espresso claims that there is no need for `Thread.sleep()` but my code doesn&#39;t work unless I include it. I am connecting to an IP and, while connecting, a progress dialog is shown. I need a `Thread.sleep()` call to wait for the dialog to dismiss. This is my test code where I use it: 

        IP.enterIP(); // fills out an IP dialog (this is done with espresso)

        //progress dialog is now shown
        Thread.sleep(1500);

        onView(withId(R.id.button).perform(click());

I have tried this code without the `Thread.sleep()` call but it says `R.id.Button` doesn&#39;t exist. The only way I can get it to work is with the `Thread.sleep()` call.

Also, I have tried replacing `Thread.sleep()` with things like `getInstrumentation().waitForIdleSync()` and still no luck. 

Is this the only way to do this? Or am I missing something? 

Thanks in advance. 

Espresso: Thread.sleep( )

I have to use Automated UI test tool and I am confused between using Robotium vs Google Espresso.

What are the major differences between the two? Are there features that exist in one but not the other?

Google Espresso or Robotium

How can I use Espresso to click a specific view inside a **RecyclerView** item? I know I can click the item at position 0 using:

`onView(withId(R.id.recyclerView))
.perform(RecyclerViewActions.actionOnItemAtPosition(0, click()));`

But I need to click on a specific view inside that item and not on the item itself.

Thanks in advance.

-- edit --

To be more precise: I have a **RecyclerView** (`R.id.recycler_view`) which items are **CardView** (`R.id.card_view`). Inside each **CardView** I have four buttons (amongst other things) and I want to click on a specific button (`R.id.bt_deliver`).

I would like to use the new features of Espresso 2.0, but I&#39;m not sure that is possible.

If not possible, I wanna use something like this (using Thomas Keller code):

    onRecyclerItemView(R.id.card_view, ???, withId(R.id.bt_deliver)).perform(click());

but I don&#39;t know what to put on the question marks.

Using Espresso to click view inside RecyclerView item

When building I get the following error: 

    Conflict with dependency &#39;com.android.support:support-annotations&#39;. Resolved versions for app (23.1.0) and test app (23.0.1) differ.

These are my gradle dependencies

    dependencies {
        compile fileTree(include: [&#39;*.jar&#39;], dir: &#39;libs&#39;)
        compile &#39;com.android.support:support-v4:23.1.0&#39;
        compile &#39;com.android.support:appcompat-v7:23.1.0&#39;
        compile &#39;com.android.support:design:23.1.0&#39;
        compile &#39;com.android.support:cardview-v7:23.1.0&#39;
        compile &#39;com.android.support:recyclerview-v7:23.1.0&#39;
        compile &#39;com.squareup.retrofit:retrofit:1.9.0&#39;
        compile &#39;com.squareup.okhttp:okhttp:2.4.0&#39;
        compile &#39;com.squareup.picasso:picasso:2.5.2&#39;
        compile &#39;com.jakewharton:butterknife:7.0.1&#39;
        compile &#39;com.squareup:otto:1.3.8&#39;
        compile &#39;com.snappydb:snappydb-lib:0.5.2&#39;
        compile &#39;com.esotericsoftware.kryo:kryo:2.24.0&#39;
        compile &#39;com.google.dagger:dagger:2.0.1&#39;
        apt &#39;com.google.dagger:dagger-compiler:2.0.1&#39;
        compile &#39;javax.annotation:javax.annotation-api:1.2&#39;
        compile &#39;io.reactivex:rxandroid:1.0.1&#39;
        compile &#39;io.reactivex:rxjava:1.0.14&#39;
        compile &#39;com.google.android.gms:play-services-location:8.1.0&#39;
        compile &#39;com.google.android.gms:play-services-gcm:8.1.0&#39;
        compile &#39;org.apache.commons:commons-lang3:3.4&#39;
        testCompile &#39;junit:junit:4.12&#39;
        testCompile &#39;org.hamcrest:hamcrest-library:1.3&#39;
        testCompile &#39;org.mockito:mockito-core:1.10.19&#39;
        androidTestCompile &#39;com.android.support.test:runner:0.4&#39;
        androidTestCompile &#39;com.android.support.test:rules:0.4&#39;
        androidTestCompile &#39;com.android.support.test.espresso:espresso-core:2.2.1&#39;
        androidTestCompile &#39;com.android.support.test.espresso:espresso-intents:2.2.1&#39;
        androidTestCompile &#39;com.android.support.test.espresso:espresso-web:2.2.1&#39;
        debugCompile &#39;com.squareup.leakcanary:leakcanary-android:1.3.1&#39;
        releaseCompile &#39;com.squareup.leakcanary:leakcanary-android-no-op:1.3.1&#39;
    }

How can I fix this?

Conflict with dependency &#39;com.android.support:support-annotations&#39;. Resolved versions for app (23.1.0) and test app (23.0.1) differ

I&#39;m new to Android and I&#39;ve seen example code using these annotations. For example:

    @SmallTest
    public void testStuff() {
        TouchUtils.tapView(this, anEditTextView);
        sendKeys(&quot;H E L P SPACE M E PERIOD&quot;);
        assertEquals(&quot;help me.&quot;, anEditTextView.getText().toString());
    }

What does that annotation accomplish?

What is the purpose of @SmallTest, @MediumTest, and @LargeTest annotations in Android?

I&#39;m trying to write some tests with the new [android-test-kit (Espresso)][1]. But I can&#39;t find any information on **how to** check if a dialog is displayed and perform some actions on it (like clicking the positive and negative buttons, e.t.c.). Note that a dialog may be also displayed by a `WebView`, not by the application it self.

Any help would be appreciated. I just need a link, or some example code for the basics:

 1. Check if a dialog appears
 2. Perform clicks on dialog buttons
 3. Interact with the dialog&#39;s inner view (if it&#39;s a custom view)
 4. Preform clicks outside the dialog, and check if it&#39;s displaying or not (for example if `setCancelable(false)` was called on the dialog builder and we want to check that)

Thank you in advice!

  [1]: https://code.google.com/p/android-test-kit/

Check if a dialog is displayed with Espresso

I am trying to test the absence of the UI view. The view selector is as follows:

    public static ViewInteraction onMyTestUi() {
        return onView(withId(R.id.myTestId));
    }
	
The selector works fine to check if the view is displayed, but gives error on checking if the view not displayed. I am using this as follows:

     onMyTestUi().check(matches(not(isDisplayed())));


But I get the following error:

&gt;  com.google.android.apps.common.testing.ui.espresso.NoMatchingViewException:
&gt; No views in hierarchy found matching: with id: is &lt;some number&gt;  If
&gt; the target view is not part of the view hierarchy, you may need to use
&gt; Espresso.onData to load it from one of the following
&gt; AdapterViews:android.widget.ListView{...}

This is strange. I am checking the absence of the UI and its expected that this view won&#39;t be found. Then why Espresso is throwing error? 
Please suggest what might be going wrong here.

Thanks,
Amazed!


matches(not(isDisplayed())) fails with NoMatchingViewException

I&#39;m having trouble importing some of the Android UI testing framework classes - I just can&#39;t figure out what is going wrong!

This is my class:

    @RunWith(AndroidJUnit4.class)
    @LargeTest
    public class ExampleUnitTest {

    @Rule
    public ActivityTestRule&lt;MainActivity&gt; mActivityRule = new ActivityTestRule(MainActivity.class);

    @Test
    public void listGoesOverTheFold() {
        onView(withText(&quot;Hello world!&quot;)).check(matches(isDisplayed()));
      }
    }

But for some reason I get the errors &#39;cannot find symbol ActivityTestRule&#39; and &#39;cannot find symbol AndroidJUnit4&#39;. I&#39;ve tried to import them but they cannot be found.

The dependencies in build.gradle are set to:

    compile fileTree(dir: &#39;libs&#39;, include: [&#39;*.jar&#39;])
    testCompile &#39;junit:junit:4.12&#39;
    compile &#39;com.android.support:appcompat-v7:23.4.0&#39;
    androidTestCompile &#39;com.android.support:support-annotations:23.4.0&#39;

    androidTestCompile &#39;com.android.support.test:runner:0.4&#39;
    androidTestCompile &#39;com.android.support.test:rules:0.4&#39;
    androidTestCompile &#39;com.android.support.test.espresso:espresso-core:2.2.1&#39;
    androidTestCompile &#39;com.android.support.test.uiautomator:uiautomator-v18:2.1.2&#39;

So I think I have all the dependencies setup - I&#39;ve been trying many things but with no luck.

Anyone have any ideas?

Why can&#39;t I import AndroidJUnit4 and ActivityTestRule into my unit test class?

Would anyone know how to test for the appearance of a Toast message in android espresso? In robotium its easy &amp; I used but started working in espresso but dont getting the exact command.

Checking toast message in android espresso

I got a error when i run android espresso test:

&gt; com.google.android.apps.common.testing.ui.espresso.PerformException: Error performing &#39;single click&#39; on view &#39;with id: is &lt;2131034173&gt;&#39;.

My code is easy:

    onView(withId(R.id.btn)).perform(click());

But there is no error with this code:

    onView(withId(R.id.btn)).check(matches(isDisplayed()));
	
I can not find the cause why it happen.

PerformException: Error performing &#39;single click&#39;

I was seeking for test frameworks for Android UI automation and I stumbled upon `UI Automator` and `Espresso` and this is the part I am confused about -

 1. Both are maintained by Google
 2. Both are used for functional UI testing
 3. Both are `Android` only frameworks

So my questions/doubts here are -

 - What is the major difference between `UI Automator` and `Espresso`?
 - Will the source code have to be modified to integrate any of these frameworks?
 - Does one framework hold any advantage over the other? If yes, then which framework is the most suitable for UI automation of an Android app? 


Android Testing: UIAutomator vs Espresso

The new permissions scheme introduced by Android Marshmallow requires checking for specific permissions at runtime, which implies the need to provide different flows depending on whether the user denies or allows access.

As we use Espresso to run automated UI tests on our app, how can we mock or update the state of the permissions in order to test different scenarios?

Android Marshmallow: Test permissions with Espresso?

Quite simply, how do I say if a given `TextView` contains a specific string in `Espresso`.

The equivalent of: `myStrings.contains(&quot;Subby&quot;);`

Espresso - TextView contains String

I&#39;m trying to run a local unit test that depends on the context, and was following this guide: https://developer.android.com/training/testing/unit-testing/local-unit-tests#kotlin  and I set up my project like this (following this link : https://developer.android.com/training/testing/set-up-project ):

**build.gradle(app)**

    android {
    compileSdkVersion 28
    buildToolsVersion &#39;27.0.3&#39;
    defaultConfig {
        minSdkVersion 21
        targetSdkVersion 27
        versionCode 76
        versionName &quot;2.6.0&quot;
        testInstrumentationRunner &quot;androidx.test.runner.AndroidJUnitRunner&quot;
        multiDexEnabled true

    useLibrary &#39;android.test.runner&#39;
        useLibrary &#39;android.test.base&#39;
        useLibrary &#39;android.test.mock&#39;

    }
    testOptions {
        unitTests.returnDefaultValues = true
        unitTests.all {
            // All the usual Gradle options.
            testLogging {
                events &quot;passed&quot;, &quot;skipped&quot;, &quot;failed&quot;, &quot;standardOut&quot;, &quot;standardError&quot;
                outputs.upToDateWhen { false }
                showStandardStreams = true
            }
        }
        unitTests.includeAndroidResources = true

    }
    dependencies {
    implementation fileTree(include: [&#39;*.jar&#39;], dir: &#39;libs&#39;)

    androidTestImplementation(&quot;androidx.test.espresso:espresso-core:$espressoVersion&quot;, {
        exclude group: &#39;com.android.support&#39;, module: &#39;support-annotations&#39;
    })
    // Espresso UI Testing dependencies
    implementation &quot;androidx.test.espresso:espresso-idling-resource:$espressoVersion&quot;
    androidTestImplementation &quot;androidx.test.espresso:espresso-contrib:$espressoVersion&quot;
    androidTestImplementation &quot;androidx.test.espresso:espresso-intents:$espressoVersion&quot;

    testImplementation &#39;androidx.test:core:1.0.0&#39;

    // AndroidJUnitRunner and JUnit Rules
    androidTestImplementation &#39;androidx.test:runner:1.1.0&#39;
    androidTestImplementation &#39;androidx.test:rules:1.1.0&#39;
    // Espresso Assertions
    androidTestImplementation &#39;androidx.test.ext:junit:1.0.0&#39;
    androidTestImplementation &#39;androidx.test.ext:truth:1.0.0&#39;
    androidTestImplementation &#39;com.google.truth:truth:0.42&#39;
        implementation &#39;androidx.multidex:multidex:2.0.0&#39;
    }

My espresso_version is **espressoVersion = &#39;3.1.0&#39;**

My test that is located in ***module-name/src/test/java/*** looks like this:

        import android.content.Context
    import androidx.test.core.app.ApplicationProvider
    import com.instacart.library.truetime.TrueTime
    import edu.mira.aula.shared.extensions.android.trueDateNow
    import edu.mira.aula.shared.network.ConnectivityHelper
    import kotlinx.coroutines.experimental.runBlocking
    import org.junit.Assert
    import org.junit.Before
    import org.junit.Test
    import java.util.*
    import java.util.concurrent.CountDownLatch

    class TimeExtensionsUnitTest {
    private lateinit var instrumentationCtx: Context

    @Before
    fun setup() {
        instrumentationCtx = ApplicationProvider.getApplicationContext&lt;Context&gt;()
    }
     @Test
    fun testTrueTimeValueReturnsIfInitialized() {
        if (ConnectivityHelper.isOnline(instrumentationCtx)) {
            runBlocking {
                val countDownLatch = CountDownLatch(1)
                TrueTime.build()
                        .withSharedPreferencesCache(instrumentationCtx)
                        .withConnectionTimeout(10000)
                        .initialize()
                countDownLatch.countDown()

                try {
                    countDownLatch.await()
                    val dateFromTrueTime = trueDateNow()
                    val normalDate = Date()
                    Assert.assertNotEquals(dateFromTrueTime, normalDate)
                } catch (e: InterruptedException) {
                }
            }
        }
    }

Everytime I run it, it gives me: 

    java.lang.IllegalStateException: No instrumentation registered! Must run under a registering instrumentation.
     at androidx.test.platform.app.InstrumentationRegistry.getInstrumentation(InstrumentationRegistry.java:45)
      at androidx.test.core.app.ApplicationProvider.getApplicationContext(ApplicationProvider.java:41)
	

If I run it as a Instrumental Test(changing the package) it runs without errors.
But I thought that this guide was exactly to be able to run unit test using Android Framework classes such as Context.
I even tried run that `class UnitTestSample` but the same error occurs.

I also removed all android.support dependencies from my project

Any ideas on how to solve it?

AndroidX : No instrumentation registered! Must run under a registering instrumentation

I am using espresso-contrib to perform actions on a `RecyclerView`, and it works as it should, ex:
```java
//click on first item
onView(withId(R.id.recycler_view))
    .perform(RecyclerViewActions.actionOnItemAtPosition(0, click()));
```
and I need to perform assertions on it. Something like this:
```
onView(withId(R.id.recycler_view))
    .perform(
        RecyclerViewActions.actionOnItemAtPosition(
            0, check(matches(withText(&quot;Test Text&quot;)))
        )
    );
```
but, because [RecyclerViewActions][1] is, of course, expecting an action, it says wrong 2nd argument type. There&#39;s no `RecyclerViewAssertions` on espresso-contrib.

Is there any way to perform assertions on a `RecyclerView`?

  [1]: http://android-test-kit.googlecode.com/git-history/e81b6694887f5c73617759d2728a92beba9b8f12/docs/javadocs/espresso/espresso-contrib-2.0-javadoc/reference/android/support/test/espresso/contrib/RecyclerViewActions.html#actionOnItemAtPosition(int,%20android.support.test.espresso.ViewAction)


How to assert inside a RecyclerView in Espresso?

Using Espresso and Hamcrest,

How can I count items number available in a recyclerView?

Exemple: I would like check if 5 items are displaying in a specific RecyclerView (scrolling if necessary).



How to count RecyclerView items with Espresso

In my test, after one action, there are two possible views which can appear and both of them are correct. How can I check if one of the view is displayed. For a single view I can check with is Displayed(). But that would fail if other view is visible instead. I want to pass the test if any one of those two views are displayed.

    onMyButton.perform(click());
	
    onMyPageOne.check(matches(isDisplayed())); //view 1
    or
    onMyPageTwo.check(matches(isDisplayed())); //view 2
		
After, perform click on MyButton, any one of the view (1 or 2) is expected to appear but not both. It is not fixed that which one would be displayed. 
How can I check if any one of them is displayed?

Espresso - How to check if one of the view is displayed

Having gridView which has some images. The gridView&#39;s cell comes out from same predefined layout, which has same id and desc.

&gt; R.id.item_image == 2131493330

    onView(withId(is(R.id.item_image))).perform(click());

Since all cells in the grid have same id, it got `AmbiguousViewMatcherException`.
How to just pick up first one or any of one of them?
Thanks!

&gt; android.support.test.espresso.AmbiguousViewMatcherException: &#39;with id: is &lt;2131493330&gt;&#39; matches multiple views in the hierarchy.
Problem views are marked with &#39;****MATCHES****&#39; below.

&gt; +-------------&gt;ImageView{id=2131493330, res-name=item_image, desc=Image, visibility=VISIBLE, width=262, height=262, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0} ****MATCHES****

&gt; +-------------&gt;ImageView{id=2131493330, res-name=item_image, desc=Image, visibility=VISIBLE, width=262, height=262, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0} ****MATCHES****
|


In Espresso, how to avoid AmbiguousViewMatcherException when multiple views match

the following is one of my Espresso test cases.

        public void testLoginAttempt() {
            Espresso.onView(ViewMatchers.withId(R.id.username)).perform(ViewActions.clearText()).perform(ViewActions.typeText(&quot;nonexistinguser@krossover.com&quot;));
            Espresso.onView(ViewMatchers.withId(R.id.username)).perform(ViewActions.clearText()).perform(ViewActions.typeText(&quot;invalidpassword&quot;));
    
            Espresso.onView(ViewMatchers.withId(R.id.login_button)).perform(ViewActions.click());
            // AFTER CLICKING THE BUTTON, A NEW ACTIVITY WILL POP UP.
            // Clicking launches a new activity that shows the text entered above. You don&#39;t need to do
            // anything special to handle the activity transitions. Espresso takes care of waiting for the
            // new activity to be resumed and its view hierarchy to be laid out.
            Espresso.onView(ViewMatchers.withId(R.id.action_logout))
                    .check(ViewAssertions.matches(not(ViewMatchers.isDisplayed())));
    
        }

Currently what I did was to check if a view in the new activity (R.id.action_logout) is visibible or not. If visible, I will assume tha the activity opened successfully.
But it doesn&#39;t seem to work as I expected.
Is there a better way to check if a new activity is successfully launched instead of checking a view in that activity is visible?
Thanks



All Android Espresso Solutions on Gang of Coders

Total of 21 Android Espresso Solutions