Don't be mocked by your Mocks: Listening to your Tests
Ғылым және технология
This is a virtual Meetup occurring at 5PM UK time (GMT). Join the live broadcast on www.virtualjug.com
View the event in your timezone:
Take part in the live session discussion on our #live-session slack channel: bit.ly/337QHTE
The recording will be available immediately afterward.
Abstract:
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
Пікірлер: 4
Really good talk. I wish KZread allowed me to give more than a single "like".
You called out a link at around 38:30 (Yan Cooper?) but you didn't make it publically available. Also, 01:03:30 is probably the most useful slides in this presentation. This is a really good talk that consolidates years of experience of testing that summarizes the current thinking on this subject. I also appreciate the general approach to the subject instead of focus on Java and would consider it a quality talk for General DEVOPs.
Great. but , lack of real example. Some point is hard to understand and feel the real meaning.
Slides - t.co/VFFNO9AAgg?amp=1