In part 3, I’ve started explaining how contract-based testing works. To that end, I’ve talked about the provider-driven approach. In this part, I want to add to that by talking about the consumer-driven approach. There is more to unpack here than in the provider-driven approach. …

In part 1, I’ve talked about what contract-based testing is. In part 2, I continued with why we should prefer contract-based testing over end-to-end testing. In this part, I want to start with how contract-based testing works. While doing so, I’ll also go into the details of the provider-driven approach…

In part 1, I’ve talked about the basics of contract-based testing. I haven’t talked about the specifics of contract-based testing yet, I will do so in part 3. Before I dive deep into the details of contract-based testing I want to take a small step back to talk about end-to-end…

Modern software architecture promotes building tightly scoped, reusable applications. Because of this, big organisations have hundreds of applications working together at any given time. These applications talk to each other via their interfaces. These complex networks of applications can cause hard-to-trace bugs which are often difficult to test. Contract-based testing…

TL;DR: See Conclusion. Prefer reading Dutch? I’ve been a software tester for a little over a year and a half now. In that period the number of times I had to test something manually can be counted on one hand. Yet every time I Google something related to testing I…

I could not find a good human-readable resource about Problem. Therefore I’m writing it myself. What is Problem JSON Problem is a standardized way of describing any kind of error thrown by an API. A Problem can be described in JSON or XML, but we’re only going to talk about the JSON variant in…