Abstract
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 to IdlingResource.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2019 Denys Zelenchuk
About this chapter
Cite this chapter
Zelenchuk, D. (2019). Handling Network Operations and Asynchronous Actions. In: Android Espresso Revealed. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4315-2_4
Download citation
DOI: https://doi.org/10.1007/978-1-4842-4315-2_4
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-4314-5
Online ISBN: 978-1-4842-4315-2
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)