Want to test Android Apps ? , Go for Espresso !!!
Use Cases and Deployment Scope
Pros
- Automatic Waiting logic before failing any test
- Black box and Grey box testing
- Easy to Understand and Very Flexible
- Supported Java And Kotlin
- Fewer Efforts compare to other Mobile Automation Frameworks
- Execution is very Fast
Cons
- As Espresso works on the ideal thread if the threads are not handled properly by the developing team it can lead to challenges in the execution of your tests.
- Depends more on the developer's code
- we cannot develop tests as individual frameworks, we share the repository with developers.
- We need to be cautious while making changes in the tests, as we share same repository
Likelihood to Recommend
- It is very easy to verify Images with drawable resources
- Color Verification we can do this by referring to the same hex code as the developer team used so that it is reused.
- Opening a desired activity without performing End-to-end flow which eventually saves time.
- If the application is built on Android we can go testing activity with Espresso as it provides all the necessary APIs
- Espresso is not appropriate to iOS app automation, from a business point of view we need to hire new resources for iOS testing.
