Why we chose Playwright for our testing needs
Use Cases and Deployment Scope
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
Likelihood to Recommend
Playwright is works pretty well for automating the critical user paths of any web application, ensuring that core functionalities are constantly tested and catching issues before they reach QA, particularly through its seamless integration into our CI/CD (in our case, using GithHub); however, it is less appropriate for mobile testing since it doesn't support mobile applications. Testers still needs to learn another framework to do this.
