What Is Agile Testing? Definitions, Roles, Principles, Practices and Guidelines

What Is Agile Testing?

Agile testing is a team activity that involves both developers and testers; the goal is to deliver increments that have been coded, integrated, and tested, rather than just coded.

Broadly, testing is part of the whole agile team’s work, and developers must help test stories when testing backlog builds up. Narrowly, agile testing focuses on how testers think and act within an agile development context.

Agile Testing Personnel

Agile testers are professional testers who adapt to change, collaborate closely with developers and business people, and use testing to capture requirements and drive development. They possess strong technical skills, can automate tests, perform exploratory testing, and understand customer needs.

In a Scrum‑based agile team, the product owner defines vision and ROI, the Scrum Master leads the team, and the development team (including front‑end, back‑end, and testing skills) implements the product.

Agile Testing Mindset

Provide continuous feedback to clarify user stories.

Create testable stories together with the team.

Execute tests collaboratively and receive valuable feedback.

Focus on delivering customer value by prioritising core functionality first.

Encourage developers to write tests early (test‑first) and adopt TDD/ATDD/BDD.

Maintain courage to test early, automate, and improve continuously.

Simplify designs and testing approaches.

Continuously improve skills and processes.

Respond to change together with developers.

Self‑organise and share responsibility for quality.

Respect people and foster a fun, collaborative environment.

Ten Agile Testing Rules

Provide continuous feedback – clarify requirements and turn stories into executable tests.

Create customer value – focus on the critical path, automate golden‑path tests, add negative and boundary tests, consider security, and plan test effort in iteration planning.

Communicate face‑to‑face – testers work directly with developers, product owners, business reps, and users.

Courage – test early, drive agile transformation, practice test‑first, automate, allow mistakes, and speak for the team.

Simplify – write clean code, use lightweight tools, and apply appropriate test layering.

Continuous improvement – keep learning, improving, and delivering value.

Respond to change – balance focus and change, with automation as a key enabler.

Self‑organisation – the whole team owns delivery and quality.

People‑centric – respect each member, encourage skill growth, and let anyone contribute to testing.

Enjoy the work – foster passion and avoid blame culture.

Agile Testing Process Strategy

In each iteration, work proceeds story by story: story design → story development → story testing → story acceptance → story release. This prevents a mini‑waterfall and enables test‑left, continuous testing, and test‑first practices.

Test‑first means testing activities start early, not waiting until the end of the iteration. TDD (Test‑Driven Development) has developers write failing tests before code, then refactor. ATDD/BDD involve the whole team defining acceptance tests together.

Test Automation Pyramid

Since Mike Cohn introduced the test automation pyramid in 2003, teams consider which layers to automate: unit tests at the base, service/integration tests in the middle, and UI/acceptance tests at the top. Extensions add exploratory testing (the “god’s eye”) and additional quality dimensions.

Agile Testing Quadrants

The quadrants visualise four testing categories: technology‑facing tests that support the team (unit, component), business‑facing tests that critique the product (functional, exploratory), and the surrounding layers for performance, security, and regression.

Agile Testing Manifesto

The manifesto emphasises customer focus, results, collaboration, creativity, learning, and delivering business value through testing.

For further reading, see the linked articles and images throughout the original source.

Event Notice

On December 3 (Thursday) at 8 pm, a live session titled “Agile Environment Test Automation” will be held by Chen Xiaopeng, test‑automation lead at Deloitte, with QR‑code registration.