One of the key benefits of the Espresso framework is its test robustness. It is achieved through automatic synchronization of most of the test actions. Espresso waits for the main application UI thread while it is busy and releases test actions after the UI thread becomes idle. Moreover, it also waits for AsyncTask operations to complete before it moves to the next test step. In this chapter, we will see how Espresso can handle network operations using the IdlingResource mechanism and become familiar with the ConditionWatcher mechanism as an alternative ...
© Denys Zelenchuk 2019
Denys ZelenchukAndroid Espresso Revealedhttps://doi.org/10.1007/978-1-4842-4315-2_44. Handling Network Operations and Asynchronous Actions
Denys Zelenchuk1
(1)
Zürich, Switzerland
Get Android Espresso Revealed: Writing Automated UI Tests now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
