android / android/android-test

Espresso test failed, no feedback to help me figure out why

Open
#1,893 14 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
1.2k
Forks
342
Avg merge
11h 29m
Merged PRs (30d)
2

Description

### Description
As far as I know, I'm writing my Espresso tests correctly. However, they fail when I run them, and there's nothing that's telling me _why_ they fail so I can fix them. There's no stack trace, no assertion errors in logs, nothing.

### Expected Results
In theory, my test should pass.

### Actual Results
The test fails, with no information or indication of why it failed.

Here are my only logs. Good luck finding the cause from them.
[connected.zip](https://github.com/android/android-test/files/12384047/connected.zip)

### AndroidX Test and Android OS Versions
```
androidx.test:core:1.5.0
androidx.test.espresso:espresso-core:3.4.0
androidx.test.ext:junit-ktx:1.1.5
androidx.test:runner:1.5.2
androidx.test:rules:1.5.0
```

Android 10, Android 13

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Espresso failure with the listed AndroidX Test versions on Android 10 or Android 13, then inspect connected.zip and the available logs. Done means the failing test produces actionable diagnostic output, such as a stack trace or assertion error, that explains the cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.