3 years ago

Category: Data, github

Over the course of several posts, we have seen how, as a result of the evolution of application architectures, new needs arise in the field of testing. We have focused on a specific one: as important as testing the functionalities in consumer and producer independently is, so also is ensuring that the interaction between them is correct. We have seen that we have Contract Testing within our reach, with different approaches and tools that allow us to address this specific need.

We run ./mvnw clean install and we see that although we have changed the contract with Spring Cloud Contract, the tests are autogenerated, so everything goes according to plan and we don’t have to touch anything in the producer.

The truth is that we have a tendency to discover a tool, and if we like it and it suits us, to use it indiscriminately.