44

Sometimes, while Espresso testing, I see the following exception.

Test instrumentation process crashed.  Check package_name.TestName#methodName.txt for details

Where is this .txt file stored? I can't seem to find it anywhere.

Use Case

In Jenkins (CI), I want the logs to see exactly what stacktrace caused the crash.

ZakTaccardi
  • 12,212
  • 15
  • 59
  • 107
  • 6
    Possible duplicate of [How to see the Android Orchestrator log?](https://stackoverflow.com/questions/46435789/how-to-see-the-android-orchestrator-log) – tir38 Jun 04 '18 at 20:36

5 Answers5

25

If you are working with an emulator, in A.S open Device File Explorer and go to: /data/user_de/0/android.support.test.orchestrator/files/, then you can look for a particular file there

EDIT: June 25 - 2019 >> If you have updated to AndroidX dependencies, then the .txt file is located in /data/user_de/0/androidx.test.orchestrator/files/

Carlos Daniel
  • 2,459
  • 25
  • 30
8

In my case, it was simpler to just check Logcat, rather than listen to that recommendation

Shalbert
  • 1,044
  • 11
  • 17
4

For others encountering this issue, as @antek pointed out the files might not be accessible on a non-rooted device. You might try using an emulator running a non-Google Play API where you can obtain a root shell.

adb root
adb shell
ls /data/data/androidx.test.orchestrator/files

Alternatively, you could try running the tests using the debugger.

user650881
  • 2,214
  • 19
  • 31
4

I could not find the text file, but I was able to get logcat and view the fatal that caused the orchestrator to crash

first I clear the logcat

adb logcat -c

then I run the test, then I grab the logcat

adb logcat > ~/Desktop/logcat

then I open logcat file and search for string FATAL

the_prole
  • 8,275
  • 16
  • 78
  • 163
-1
  1. I just did wipe data in Android studio for my emulator using Device manager.
  2. Restarted the emulator and run the test works for me
Vikas
  • 1