Why we chose Playwright for our testing needs
July 01, 2024
Why we chose Playwright for our testing needs
![Anonymous | TrustRadius Reviewer](https://static.trustradius.com/r/d4528173fc41413f53148c502d0996e8d0e96107/images/no_photo.png)
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Playwright
We use Playwright to automate our LMS's critical path. It is a complex software with many possible edge cases, it takes 2 testers 3 full days to fully smoke the app (not regression). With Playwright we automated the critical path, we integrated it into our CI/CD, and now it's constantly running and detecting errors and bugs before they even reach to QA.
Pros
- automation
- integrations
- support
- community
- features
- easy to use
- documentation
Cons
- bigger adoption
- mobile testing
- Reduce of cost of manual testers
- Reduce of released bugs
- Reduce of costs of developer time
- Increase QA Coverage
We selected Playwright over the rest for several reasons. The learning curve is faster, making it easier for our team to get up to speed quickly. The setup is pretty straithtforwared, minimal configurartion needed and a great example included in the configuration which includes all the basics to start writing using that spec as a placeholder. Compared to Cypress, Playwright support multiple browsers out of the box, giving us broader testing coverage. Appium is great for mobile testing, but extremely slow.
Do you think Playwright delivers good value for the price?
Yes
Are you happy with Playwright's feature set?
Yes
Did Playwright live up to sales and marketing promises?
Yes
Did implementation of Playwright go as expected?
Yes
Would you buy Playwright again?
Yes
Comments
Please log in to join the conversation