Skip to main content
Agile Testing

Agile Testing

Testing practices adapted for Agile development — continuous, collaborative, and embedded in the development process.

Full definition

Agile testing integrates testing throughout the development process rather than treating it as a separate phase. In Agile teams, testing is everyone's responsibility, and QA is embedded in the development team.

Key principles of Agile testing:

  • Testing is continuous: Not a phase at the end, but ongoing throughout the sprint
  • Whole team approach: Developers, QA, and PO all share quality responsibility
  • Fast feedback: Automated tests provide immediate feedback on changes
  • Working software over documentation: Focus on testing the product, not generating documents
  • Adapt and improve: Retrospectives drive testing process improvement

Agile testing quadrants (Brian Marick):

  • Q1 (Technology, Team): Unit tests, component tests
  • Q2 (Business, Team): Functional tests, examples, prototypes
  • Q3 (Business, Critique): Exploratory testing, usability testing
  • Q4 (Technology, Critique): Performance, security, scalability

Daily QA activities in a sprint:

  • Participate in standups
  • Review/refine user stories and acceptance criteria
  • Write and execute tests alongside development
  • Automate regression tests
  • Participate in sprint review and retrospective

Learn more about agile testing in practice

Manual Testing track