[Espresso]Test instrumentation process crashed. After click action app should restarted but with espresso is crashed about testing-samples HOT 11 CLOSED

Oh I just noticed in your description "2-After clicking on this button, the app should be restarted (Expected Result)'. You cannot restart the app from within an instrumented test, because that will kill the process the test is running in.

If you need to do this you might want to look into using UiAutomator, and setting up your tests so they run in a different process than the application under test.

from testing-samples.

Can you provide a complete sample and/or a logcat? The list of dependencies look a bit strange with a mixture of very old and new dependencies. eg The ' androidTestImplementation 'com.android.support.test:rules:1.0.2'' especially seems wrong

from testing-samples.

Can you provide a complete sample and/or a logcat? The list of dependencies look a bit strange with a mixture of very old and new dependencies. eg The ' androidTestImplementation 'com.android.support.test:rules:1.0.2'' especially seems wrong

This is the complete very simple test case
and no problem with ' androidTestImplementation 'com.android.support.test:rules:1.0.2'' especially seems wrong
i remove it and the same error happen

@RunWith(AndroidJUnit4.class)
public class SplashActivityTest{

    @Rule
    public ActivityScenarioRule<SplashActivity> mActivityScenarioRule =
            new ActivityScenarioRule<>(SplashActivity.class);

    @Test
    public void splashActivityTest(){

        onView(withId(R.id.preliveButton)).perform(click());

from testing-samples.

Sorry but without a full sample or logcat our ability to help is going to be limited. I tried copying over your list of dependencies into a simple sample project and it worked fine. You can use one of http://github/android/testing-samples as a base

from testing-samples.

Collaborator

but this is a hard restart, this button should be clicked at the start of the process to can select the environment
and after clicking, the app will hard restart.
so can't handle this case with espresso?

from testing-samples.

Oh I just noticed in your description "2-After clicking on this button, the app should be restarted (Expected Result)'. You cannot restart the app from within an instrumented test, because that will kill the process the test is running in.

If you need to do this you might want to look into using UiAutomator, and setting up your tests so they run in a different process than the application under test.

and how can i use UiAutomator to can continue my test cases after restarting app?

from testing-samples.

Espresso will wait for the app to be idle after the click is sent, so I strongly suspect this case cannot be handled in espresso. How does the code under test restart the app?

For UiAutomator, check out https://github.com/android/testing-samples/tree/main/ui/uiautomator/BasicSample. You'll likely need to adjust the targetProcess here

from testing-samples.

Espresso will wait for the app to be idle after the click is sent, so I strongly suspect this case cannot be handled in espresso. How does the code under test restart the app?

For UiAutomator, check out https://github.com/android/testing-samples/tree/main/ui/uiautomator/BasicSample. You'll likely need to adjust the targetProcess here

testing-samples/ui/uiautomator/BasicSample/app/src/androidTest/AndroidManifest.xml

Line 9 in d603281

<instrumentation android:targetPackage="com.example.android.testing.uiautomator.BasicSample"

to com.example.android.testing.uiautomator.BasicSample.test and perhaps make other changes

The screen asks you to choose the required data then the app restarts with the data you choose before.

Intent i = activity.getBaseContext().getPackageManager().getLaunchIntentForPackage(activity.getBaseContext().getPackageName());
i.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);
i.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
activity.startActivity(i);
activity.finishAffinity();
System.exit(0);
```

> and i will check uiautomator, Thanks

from testing-samples.

Yeah there isn't a way to handle a System.exit(0) from an instrumentation test that runs in the same process

from testing-samples.

Yeah there isn't a way to handle a System.exit(0) from an instrumentation test that runs in the same process

yea I tried UI Automator and instrumentation crushed also, so is there any way to handle this case?

from testing-samples.

Did you configure the UI Automator instrumentation to run in a different process than the app under test? See the manifest link I gave above

from testing-samples.