Skip to main content
Strategy & Process

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 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 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 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.

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.

Related Terms

Explore related glossary terms to deepen your understanding.

Shift-Left TestingShift-left testing is the practice of moving testing activities earlier in the software development lifecycle, catching defects during requirements, design, and development rather than after deployment.
Continuous TestingContinuous testing is the practice of executing automated tests at every stage of the CI/CD pipeline, providing immediate feedback on the risk level of each code change as it moves toward production.
Acceptance CriteriaAcceptance criteria are specific, testable conditions that a user story or feature must satisfy to be considered complete and accepted by the product owner.
Definition of DoneThe Definition of Done (DoD) is a shared checklist of quality conditions that every user story, feature, or increment must meet before it can be considered complete, covering aspects like testing, documentation, code review, and deployment readiness.
Test StrategyA test strategy is a high-level document that defines the testing approach, objectives, scope, types of testing, environments, tools, and risk mitigation for a project or organization.

Related Resources

Dive deeper with these related interview prep pages.

QA Engineer Interview PrepQA Methodology QuestionsQA Mock Interview Practice

Ready to Ace Your QA Interview?

Practice explaining agile testing and other key concepts with our AI interviewer.

Join 1,200+ QA engineers already practicing with AssertHired.

Start Your Free QA Interview

Free to start · 7-day trial on paid plans

Written by Aston Cook, Senior QA EngineerLast updated: March 2026