Please log in to watch this conference skillscast.
Consumer-driven contract testing is “alright” because it provides a way of testing contracts separately from both the client and the server. However, it creates problems of its own: it’s time consuming, complex to set up properly in your CI/CD environment, it’s boring and ultimately work you don’t need to do!
Wouldn’t it be better if you could check which versions of your interfaces work well together at compile time. Wouldn’t it be great if compatibility came for free (yes, like free beer!), with no extra effort required to test? In fact, wouldn’t it be great if instead of adding to your workload, it reduced the amount of work you needed to do so that you work less and play harder? Wouldn’t it be great if introducing something new to 100 micro-services were as trivial as hacking away a couple of lines of code, something we all do day-to-day?
At Landbay, they’ve used Swagger to help boost their confidence in API compatibility. So, they’ll show you the benefits they gleaned, lots of code and a demo of how easy it was to gain significant benefits, quickly. Chris will also share with you how it’s helped speed up and shape other testing they do (e.g. business use case testing, etc.) thanks to all their interfaces are normalised.
YOU MAY ALSO LIKE:
Lightning Talk: CDC testing is dead – Long Live Swagger!
Chris joined Landbay, a peer-to-peer fin-tech start up, as the lead software engineer. With 10+ years’ of commercial experience, he designed, developed and continues to deliver the microservice architecture that was built from the ground-up to several dozens of microservices. Prior to working with Landbay, his most recent roles involved helping architect and develop some of the largest UK customer-facing platforms in the UK, such as the EE online shop, Three, The AA, Vodafone, etc. Outside of his work life, Chris develops some small scale open-source Bible study software.