One thing that sometimes is really underestimated, it’s the capability to have enough knowledge of (distributed) systems in which sometimes is delivered value to stakeholders. Even if you don’t give so much importance to it (and you are right…), knowledge is something that is good for soul, help avoid headaches during incidents and makes resilient to bubbles. So this is how multi-version concurrency control for database snapshots gave me some trouble.

The previous post explains the principles and motivations behind contract testing. Today we give a look to how write consumer-driven contract tests with pact and Java in a SpringBoot application.

Introduction

This is the first of a series of blog posts about Contract Testing which cover the minimum set of theory and practice necessary for an effective adoption in your team, from design to code integration.