How to solve integration issues with Contract Testing
How many times two different teams have been working on user stories that work properly on isolation but that fail drastically when they are integrated? Consumer-driven development and contract testing are there to help you.
Max 100 attendees
By the end of this course, you'll be able to:
- Understand how contract testing mitigates integration issues
- Describe the benefits of Consumer-Driven Development
- Explain the flow of contract testing and how it fits in the SDLC
Nowadays, with a proper testing strategy, following the basics of the testing pyramid, most of our products are properly tested in isolation. Often, the problems arrive when dependant products are evolved in parallel and the interface of one of them changes, breaking the integration between them. In the world of microservices, these failures can be a real bottleneck if we don´t efficiently prevent them.
The concept of Contract Testing was created to help us to mitigate communication errors between products, allowing us to test the integration without the need for a real environment.
In this workshop, we will see what Consumer-Driven Development is, its benefits, and how Contract Testing allows us to follow it.
With all that said, contract testing flow is not trivial. With the support of some activities, we will review the actors involved in contract testing and how the flow is to successfully include contracts in your projects.
Meet the Instructor
Working in quality for more than 10 years, currently as Quality Architect at The workshop. I believe in Modern Testing Principles and I try to apply them on the teams I work with. Quality is more than Testing and it is a team responsibility! A testing strategy starts with Unit Tests!