What is Agile Testing?

Agile testing is a software testing approach that follows agile development principles, continuous testing throughout the sprint, collaboration between testers and developers, and fast feedback loops rather than a separate testing phase at the end.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

In agile teams, testing is not a phase, it is an activity woven into every sprint. QA engineers participate in sprint planning (assessing testability and risk), collaborate with developers during implementation (writing automation alongside feature code), and perform exploratory testing as features are completed.

The agile testing quadrants, introduced by Brian Marick, organize testing activities into four groups: Q1 (technology-facing, guiding development) - unit tests, component tests; Q2 (business-facing, guiding development) - functional tests, acceptance tests; Q3 (business-facing, critiquing the product) - exploratory testing, usability testing; Q4 (technology-facing, critiquing the product) - performance tests, security tests.

Key agile testing practices include: writing acceptance criteria with testable scenarios before development starts, automating regression tests so they run on every commit, performing exploratory testing for each story before it is marked done, and participating in retrospectives to improve the testing process continuously.

The shift from waterfall to agile fundamentally changed the QA role. Instead of waiting for a "QA phase," testers are embedded in development teams and contribute throughout the sprint.

WHY IT MATTERS

Why interviewers ask about this.

Almost every QA interview asks about agile practices. Understanding how testing fits into scrum or kanban, and being able to describe your role in sprint ceremonies, is essential for any modern QA position.

EXAMPLE

Example scenario.

A QA engineer embedded in a scrum team reviews user stories during sprint planning, writes automation for the first story while developers work on the second, performs exploratory testing on completed features daily, and provides a test summary in the sprint review. Testing never blocks deployment because it happens continuously.

TIP

Interview tip.

Describe your daily workflow in an agile team. Mention specific ceremonies you participate in and how you collaborate with developers. The agile testing quadrants are a strong framework to reference when explaining how different test types fit into sprints.