What is agile testing?
Agile testing means quality is considered in every sprint, not bolted on in a separate test phase. Testing happens early and continuously – from the requirement (“is it testable?”) to automated regression within the sprint. The goal is fast feedback instead of late defect discovery.
Whole-team approach & the tester's role
In an agile team, quality is a team responsibility – developers write tests, the team jointly defines “done”. The tester shifts from pure defect finder to quality coach: strengthening the testability of requirements, driving automation and exploratory testing, and making risks visible. The role does not disappear – it becomes more demanding.
The test pyramid
The test pyramid orders tests by scope and speed: many fast unit tests as the base, fewer integration/API tests in the middle, few slow UI/E2E tests at the top. Inverting the pyramid (many fragile UI tests) yields slow, unstable pipelines. More on implementation: test automation.
Continuous testing in CI/CD
Continuous testing means: on every commit, automated tests run in the CI/CD pipeline and give feedback within minutes. Defects are found where they are cheapest to fix. This requires stable, fast automation – otherwise the pipeline gets ignored.
Common misconceptions
- “Agile means no documentation”: no – just as much as needed, but living (e.g. testable acceptance criteria).
- “Automation replaces testers”: no – it removes routine and frees time for exploratory testing.
- “No test management needed”: yes it is – strategy, risk and reporting still matter, just more distributed.
Read more
When does automation pay off?
The simple ROI calculation, the right candidates, typical mistakes – and realistic metrics.
Read article →What is test management?
Tasks, risk-based approach, metrics and roles – and when external test management pays off.
Read article →AI in software testing
Use cases that deliver value, clear limits – and what the EU AI Act and GDPR mean for adoption.
Read article →