Testing Quadrants


Testing quadrants, defined by Brian Marick, align the test levels with the appropriate test types in the Agile methodology.

The testing quadrants model, helps to ensure that all important test types and test levels are included in the development lifecycle. This model also provides a way to differentiate and describe the types of tests to all stakeholders, including developers, testers, and business representatives.

In the testing quadrants, tests can be business (user) or technology (developer) facing. Some tests support the work done by the Agile team and confirm software behaviour. Other tests can verify the product.


(Micro)Service boundaries are logical, not physical.

My problem with the Microservices movement is that people are applying the lessons of micro-services without having first learned the lessons of service-oriented architecture. This leads to confusion and accidental complexity.

A redditor asks:

two micro service depend[ing] on the same data storage ... is a "No No" as it can introduce lots of other complexity.

But what happens if one of the micro-service is only read only?

So here is the situation, one micro service will be an internal tool which is doing some heavy lifting and then persisting the data in the data base. And another micro-service will