Test Automation & APIs
Choosing and using test automation frameworks: Selenium, Playwright, Cypress, API testing tools, performance testing and CI/CD, compared from a working SDET point of view.
Start here
New to this topic? Read these in order.
- 1Selenium vs PlaywrightThe main choice for browser UI tests.
- 2Cypress vs PlaywrightWhich JavaScript framework fits your team.
- 3Best API testing toolsOptions for testing APIs, from free to paid.
- 4JMeter vs k6Load testing: which tool to learn first.
- 5Tests in GitHub ActionsRun your automated tests on every change.
What test automation covers here
Test automation means writing code that checks your application for you, so every change is tested quickly and the same way each time. These guides cover the three layers most QA teams automate: browser UI tests (Selenium, Playwright, Cypress), API tests (Postman, Bruno and similar tools) and load tests (JMeter and k6), plus running them in CI with GitHub Actions. Most guides compare tools head to head and end with a recommendation for who should pick which.
Some of the scripts we ran are public in our aitg-test-kits repository on GitHub.
