agile testing quadrants explained

Developer Facing Critique Tests

Customer Facing Critique Tests

Customer Facing Support Tests


Agile Testing Quadrants Explained by @rubytester

On the left: Let’s write some tests that ‘support’ our building of product. Tests that illustrate, clarify, reassure how software should behave

*Disclaimer: Not actual tests, just an illustration

On the right: Let’s write some tests that ‘critique’ product

Test that find omissions, mistakes,

incorrect assumptions

From left to right we build tests that move from ‘support’ to ‘critique’ Let’s call this support/critique dimension tests can occupy

support critique

Who is the audience? What matters to them? How are tests different for them?

Customer Facing Tests

Developer Facing Tests

support critique

create modify

secure

One layer of functionality that matters

Customer Facing

Many Layers For Both Customer and Developer

Developer Facing Developer Facing

Customer Facing

Developer Facing

Customer Facing

Many Layers from common, shared layer up, up, up closer to Customer World often seen by Developers as The World Of Endless Meetings, Memos and Reports

And from common, shared layer down closer to Developer World often seen by Customers as The World Of Endless lines with commas, semicolons, curly brackets, square brackets, dots and blinking lights 101011100011100011111

Beautiful Mess Of Software Testing


Developer Facing Support Tests

Original by Brian Marick

http://www.exampler.com/old-blog/2003/08/22/#agile-testing-project-2

http://www.exampler.com/old-blog/2003/08/22/









http://agiletester.ca/

As seen in ‘Agile Testing: The Book’ by Lisa Crispin and Janet Gregory

http://agiletester.ca/


http://sketch.odopod.com/sketches/562278

http://sketch.odopod.com/sketches/562278

agile testing quadrants explained

Technology