Download as PDF, PPTX
Espresso
- 1.
- 2. Espresso The Espresso isan API provided by Google to enable testers to think in terms of what a user might do while interacting with the android application - locating UI elements and interacting with them. Espresso also blocks the test to directly interacts with activities and views of the application because holding on to these objects. This set-up of Espresso makes it to mimic to behave like actual user, enabling the QA forum to use it for functional testing :).
- 4. Web vs Mobile- Terminologies Pages -> Activity Element -> View
- 5. How Espresso Works āStart the particular Activity/View. ā Find a particular View among the whole View hierarchy. ā Perform some action on that view. ā Make assertions on the view.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. Spoon ā Spoon simplifytasks by distributing instrumentation test execution and displaying the results in a meaningful way. ā Spoon runs the tests on multiple devices simultaneously. ā Capture screenshots of failed tests.(also for Debugging). ā Runs tests on multiple devices (Recommended to have diff specs)
- 15.
- 16. Failure Handler ā Handlesfailures that happen during test execution. ā Override handle method to have the custom implementation.
- 17. Flakiness It is highlyrecommend to turn off system animations on devices used for testing. On device, under Settings > Developer options, disable the following 3 settings: ā Window animation scale ā Transition animation scale ā Animator duration scale
- 18. Android Test Orchestrator āTool which allows you to run each of your appās tests within its own invocation of Instrumentation. ā Prevents test failures of previous test to impact the upcoming ones. ā Starts a new instance of the app with each test and closes the one from the previous test.
- 19.
- 20.
- 21. Moral of thestory QAs and Devs lived happily ever after.