Do you ❤️ Mocks? When you write your first unit tests, especially on older codebases, mocking foreign code is key to survival. But as you grow older in the craft, you start piling up hours and days wasted to refactor fragile tests or to fix bugs that those heavy mock-based tests didn't catch. And so you start looking at Mocks differently. Let's go through the key factors to consider to strike the optimal balance between what needs to be mocked away and what code should be tested in integration. There's sometimes a fine line there, often interwoven with strong emotions: "Why am I testing this?" "Argh… these tests take too long" "Can this ever really break?" etc... Among the points that we'll touch on: - Mocks vs Refactoring - Mocks vs Reliability - Fine vs Coarse Mocks - Reproducibility - Partial Mocks - Mocking Statics - Alternatives to Mocks Speakers: Victor Rentea Victor is a Java Champion and Independent Trainer with an impressive experience: thousands of developers in dozens of companies trained in dedicated company sessions. He is the founder of one of the largest developer communities in Romania, Bucharest Software Craftsmanship Community and a top international conference speaker. To find more about him, join a live masterclass or call him in for a company dedicated training: victorrentea.ro