Bolton's New Agile Testing Ecosystem

By Jonathan Clarkin | November 4, 2014

I often make reference to the Agile Quadrants model to help explain different modes of testing, and how automation is just a part of a larger domain of testing. Recently, I discovered that Michael Bolton has evolved this model into something much more comprehensive and useful.

The Traditional Agile Testing Quadrants

The original Agile Testing Quadrants, popularized by Lisa Crispin and Janet Gregory, provided a useful framework for thinking about different types of testing:

Agile Testing Quadrants

This model helped teams understand that testing isn’t just about finding bugs, but also about supporting the development process and ensuring the product meets business needs.

Bolton’s Evolution

Michael Bolton has taken this foundational concept and expanded it into a more nuanced view of the testing ecosystem. His approach recognizes that:

  1. Testing is not just about quadrants - it’s about understanding the full ecosystem of activities that contribute to product quality
  2. Context matters - what works in one situation may not work in another
  3. Human judgment is irreplaceable - automation supports testing but doesn’t replace the need for skilled testers

The New Ecosystem Thinking

Bolton’s evolved model emphasizes:

Exploration and Investigation

Rather than just executing predefined tests, testers need to actively explore the product, investigating how it behaves under different conditions and scenarios.

Risk-Based Approach

Testing activities should be prioritized based on risk, not just coverage metrics or automation percentages.

Collaborative Discovery

Testing is most effective when it’s integrated into the entire development process, not treated as a separate phase or activity.

Practical Implications

This ecosystem thinking has several practical implications for how we approach testing:

  1. Tool Selection: Choose tools that support investigation and exploration, not just execution
  2. Skill Development: Invest in developing critical thinking and investigation skills
  3. Process Integration: Embed testing activities throughout the development lifecycle
  4. Measurement: Focus on meaningful metrics that reflect actual risk reduction

Moving Forward

As the testing field continues to evolve, frameworks like Bolton’s ecosystem model help us think more holistically about quality and testing. Rather than getting caught up in debates about automation vs. manual testing, we can focus on building systems that effectively manage risk and deliver value.

The key is to remember that testing is fundamentally about learning and discovery. Any model or framework we use should support and enhance that core purpose, not constrain it.