The Test Masters series is created to experience testing in a fun and new way. Play games, use robots, experience new tooling and techniques to make yourself a better tester! During the events we organise you can try out these new tools and techniques and engage in a friendly competition with your peers. The events are a great opportunity to learn more about testing and ‘level up’ your testing craftsmanship. Reach your goal of becoming the Ultimate Test Master!
Slot 1: Tackling complexity around the heart of your service - Mattijs Meiboom (bol.com)
Slot 2: TBD
Tackling complexity around the heart of your service
Everything seemed fine at first. Then, complexity happened. Our team was happily building new features and writing tests was still fun. With every new feature, however, the amount of services we were
depending on seemed to grow and slowly we started to feel the pain. Our production code was able to evolve, our tests were not. An increasingly complex test setup started to manifest itself
into mock-hell, flaky builds, and an increasing amount of wtf's per minute. Something needed to change.
We went back to the drawing board and thought about writing our tests using the same principle we applied to structure our production code: separating technical and functional
concerns through strict boundaries. Combined with a different approach to mocking, we were able to reduce complexity and improve maintainability of our test harness.
Sharing the principles and code behind our test harness, I'll provide you with ideas on how to tackle code complexity.
Motivation/Bio: As a software engineer at bol.com, I've been working for nearly two years on replacing the customer returns process with several micro-services. Over that time, I've experienced how increasing test complexity started slowing us down. Now, I'd like to share how we applied several concepts to dig ourselves out again.