TrustRadius Insights for Espresso are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Recommendations
Users commonly recommend the following:
Download the demo and try all the features of the software, including the CSSEdit tools, Dynamo auto-building, and Server Sync.
Consider the software for MAC users, especially for web applications and static websites. It is relatively accessible in terms of price and offers a free trial. Users also suggest testing Espresso alongside other text editors like Atom and BBedit.
Use Espresso for quick coding. It is easy to use without any issues, and updates are seamless without disrupting workflow. Users highly recommend adding Espresso to one's toolbox, particularly for those who do not code frequently or struggle with syntax. Additionally, Espresso combines FTP, styling, and code writing functions, making it a practical choice for users looking for an all-in-one tool.
Note that some reviewers mention switching to alternative editors like Panic's Coda 2 or exploring other free options before considering Espresso.
We use Espresso to automate Android Automation tests on Android Tab, so the app is installed on retail store entrances which helps customers to locate the products and services and help them to save time in locating the product without any issue, Since in all the stores we have Android tablets install so Espresso is the perfect choice to automate tests, as it is speedy and reliable.
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.