QA and testing is no longer the separate-team activity it was a decade ago. In modern software organizations, developers write and own most of their tests, dedicated QA engineers focus on test infrastructure, exploratory testing, and the workflows that automation does poorly. The boundary between SDET, QA automation, and platform engineering has effectively dissolved.
The current tool landscape splits cleanly: unit tests run in the test framework native to the codebase (Vitest, Jest, pytest, JUnit, Go test), API contracts are enforced by integration tests against real services in containers, end-to-end browser tests run on Playwright (which has overtaken Selenium for new projects), and visual regression covers the rendering layer.
What you'll work with in these 21 courses
- Test pyramid: unit, integration, contract, end-to-end balancing
- Browser automation: Playwright, Cypress, Selenium
- API testing: Postman / Newman, REST Assured, Schemathesis
- Test design: AAA, given-when-then, test data builders, fixtures
- CI integration: parallel runs, sharding, flaky test triage
- Performance testing: k6, Locust, JMeter