Mobile Testing / Quiz
Espresso & the Idling Resource Pact
Espresso's superpower is waiting for the app to go quiet. Its blind spot is every thread it does not know about. Idling resources are the treaty between them.
- Difficulty
- Hard
- Format
- Quiz
- Points
- 200
- Estimate
- 11 min
// MISSION BRIEF
Your Mission
Espresso auto-synchronizes with the main thread and AsyncTasks, which is why well-built Espresso suites barely flake. But OkHttp calls, RxJava chains, and coroutines are invisible to it, and that gap is where sleeps creep back in.
Seven questions on synchronization, idling resources, and their failure modes. Speed bonus active.
// FIRST CONTACT
Battle teaser
Out of the box, Espresso automatically waits for:
- AAll network requests on any thread pool
- BThe main thread's message queue to be idle and AsyncTask pool work to finish, before running each action or assertion
- CNothing; every wait must be coded explicitly
- DA fixed 5-second settling period per action
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
espressoandroidui-testingsynchronization