Testing Microservices: Join the Revolution By Victor Rentea

Testing strategies for modern software architectures are evolving. As we transition from monolithic structures to team-sized microservices with crisp APIs aligned to bounded contexts, we encounter more stable testing surfaces. This shift leads many high-performing teams to favor integration tests over fine-grained, brittle unit tests. These integration tests, which are closer to the functional requirements, prove more trustworthy and are more resilient to internal refactoring, though they may come with a higher cost. In a vivid and engaging style, this talk addresses the primary challenges of integration testing in the microservices era: cognitive overload, test isolation, and test execution speed. Join the testing revolution and discover how to enhance your team's testing efficiency and effectiveness.
VICTOR RENTEA
Victor is a Java Champion with two decades of experience, passionate about architecture, refactoring, and unit testing. He’s the founder of the world’s largest developer community on these topics: European Software Crafters. Today Victor helps companies throughout Europe raise the bar via consultancy and intense training workshops. You can find dozens of past conference talks, a blog, and his training offer on victorrentea.ro

[@georgetarida5653]

Really fun presentation! 😃 Always a pleasure to listen to Victor!

[@oferbar]

Always a pleasure to listen to Victor!

[@botelhorui]

very good presentation flow!

[@richinex]

Such energy and knowledge

[@colberttoledo3544]

Next level speech

[@balazsklezli5702]

good stuff as always :)

[@avalagum7957]

Is there any way to start spring boot in a test suite and all test classes in that test suite use that spring boot instance?

[@anton-tkachenko]

uhm, if you inherit from one base class, spring context will start only once

[@avalagum7957]

@@anton-tkachenko uhm ... not sure if I understand what you meant.
So I have a base class like this:
@SpringBootTest class BaseClass { ... }
and a bunch of other classes like:
OneTest extends BaseClass { @Test void test1() { ... } }
TwoTest extends BaseClass { @Test void test2() { ... } }
And you said that ./gradlew test will create only 1 spring context?

[@askarkalykov]

Ok i see it's useless for those not actually using spring