In the emerging architecture of microservices, teams try to be as agile as possible.
This means that new services pop up quickly. The number of interconnections increases exponentially, making integration testing much more complex and time-consuming. How can engineers avoid compromising on quality assurance, while also maintaining an adequate delivery cadence ? What if I told you that there could be a technique, which could speed up your development lifecycle, while also increasing your confidence that your code works ? This talk will present a technique, which allows teams to gain quick feedback for new code that's introduced in a codebase, thus being able to move faster without breaking things.
Key takeaways: - A way to structure dependency injection in your service, improving maintainability - A new category of testing, something between the fields of unit testing and integration testing - How to easily enable this new category with the least amount of code - Some handy Spring tools
YOU MAY ALSO LIKE:
Acceptance Testing in the Microservices World
Dimos is a software geek with an MSc in Software Engineering and working experience from both small software shops and big tech companies. He's been working with microservices architectures for the last 4 years, constantly looking for new approaches on designing, implementing and verifying distributed systems.