// test automation · cypress → playwright
A test suite that kept up with the platform
I led the inception of the first automation suite, built on Cypress, and evolved it in CI over time alongside the Test Automation Engineers. As the suite grew, its performance suffered, so I led the switch to Playwright, which brought huge gains in performance and stability across the CI/CD environment.
How the suite evolved
- first automation suiteCypress
- grown in CIwith Test Automation Engineers
- slower as it grewperformance suffered
- switchedto Playwright
- todayfaster, more stable CI/CD
before · Cypress
The first automation suite. As it grew, its performance in CI suffered.
after · Playwright
Huge gains in performance and stability across CI/CD.
Inception
Led the creation of the first end-to-end automation suite, on Cypress.
Evolving in CI
Grew the suite inside the CI pipeline over time, alongside the Test Automation Engineers.
The switch
When performance suffered as the suite grew, led the move to Playwright.
# in practice
- Automated end-to-end testing has been part of CI since the first suite.
- The suite was built up together with the Test Automation Engineers.
- Moving to Playwright made the suite much faster and more stable in CI/CD.