Test your Espresso knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is a benefit of Espresso's design encouraging small, focused test methods that verify one specific UI interaction/outcome, rather than one large end-to-end test covering an entire user flow?
In this round
What is a benefit of Espresso's design encouraging small, focused test methods that verify one specific UI interaction/outcome, rather than one large end-to-end test covering an entire user flow?
What is Espresso-Intents used for?
What does `RecyclerViewActions.actionOnItemAtPosition()` (from the Espresso-Contrib module) allow you to do?
How would you simulate clicking a button matched by its ID in Espresso?
How would you type text into an `EditText` field in an Espresso test?
What does `ActivityScenario` (used in modern Espresso/AndroidX tests) provide for a test?
What does `pressBack()` simulate in an Espresso test?
What is the basic structure of an Espresso test statement, commonly summarized as "ViewMatchers, ViewActions, ViewAssertions"?
What does `.check(matches(isDisplayed()))` verify in an Espresso test?
Where do Espresso tests typically run, compared to local JVM-based unit tests in an Android project?
What is a common reason UI tests (Espresso included) are typically run less frequently in CI than fast unit tests?
What is `FragmentScenario`, and what testing scenario is it designed for?