Test Automation
The use of software tools and scripts to execute tests, compare results against expected outcomes, and report findings automatically, without manual intervention.
Test automation converts repeatable manual tests into scripts that can run unattended, consistently, and at scale. Automation spans multiple levels: unit tests (Jest, pytest), API tests (Postman, REST Assured), UI tests (Playwright, Cypress, Selenium), visual tests (Percy, Chromatic), performance tests (k6, Locust), and accessibility tests (axe-core).
Not all tests should be automated. The best candidates are stable, repetitive, data-driven, or high-risk tests. Exploratory testing, usability testing, and tests for rapidly changing features are often better left as manual activities. A common guideline is the test pyramid: many unit tests, fewer integration tests, and the fewest E2E tests.
Why It Matters for QA Teams
Manual testing does not scale with modern deployment frequency. Automation lets QA teams validate hundreds of scenarios in minutes, freeing human testers for creative, high-value exploratory work.
Example
A team automates their 200-test regression suite using Playwright. What previously took two QA engineers a full day of manual testing now runs in 12 minutes on every pull request. The engineers spend their reclaimed time on exploratory testing of new features and improving test coverage for edge cases.