ABSTRACT:
Unit / Integration / GUI - an obvious association when anybody mentions a test triangle. Every ISTQB student can drill down these elements when woken up in the middle of the night. The thing is: is this decomposition still relevant? Does it even work when you run a highly distributed, microservice environment? Does this make any sense in a microservices world?
During this session we will walk through different test goals, a different hypothesis we want to assert during testing, evaluate tools that can support us and see these tools in action: on a "real" java based microservices. So expect some critical thinking and a walk-through of a set of tools and methods on how to use unit and integration tests effectively. But first and foremost, we will look beyond that and look when to initialise application container, how to approach validation of the service's contracts and finally is it worth to mimic a part of production environment with test containers.
🗣 SPEAKER'S PROFILE:
Jakub is a software craftsperson with nearly two decades of commercial experience in programming - wearing multiple hats, getting hands dirty in multiple environments. Some languages, some frameworks, blah blah blah - doesn’t really matter. Architect, programmer, manager, technical trainer, tech lead, wannabe entrepreneur, JUG leader. There is a fair chance he does none of those right. Jakub divides his time between gaining hands-on project experience on Hazelcast Cloud and sharing it afterwards with the community at conferences or local Java Users Groups
コメント