Backend & Integration tech.Lunch Talk15min
How to write your own DbUnit
The talk highlights a common testing mistake—overusing APIs to build test data instead of directly seeding state—and demonstrates better practices using DbUnit, Database Rider, and generalized techniques for managing any application state to create cleaner, faster, and more reliable automated tests.
talk.summaryAiDisclaimer
Alexei BratuhinOpenValue
`Output = State + Input`, not `Output = + Input`
In my past project experience, I’ve consistently observed a recurring pattern: when automated tests are implemented at all, developers often misuse or overuse APIs to create test data before writing the actual tests, instead of simply seeding the required state or data directly within the test itself.
In this talk, I’ll demonstrate how to do it better using some powerful tools: the classic DbUnit, the modern and elegant Database Rider, and an approach to extend this paradigm to any kind of application state — not just databases.
In my past project experience, I’ve consistently observed a recurring pattern: when automated tests are implemented at all, developers often misuse or overuse APIs to create test data before writing the actual tests, instead of simply seeding the required state or data directly within the test itself.
In this talk, I’ll demonstrate how to do it better using some powerful tools: the classic DbUnit, the modern and elegant Database Rider, and an approach to extend this paradigm to any kind of application state — not just databases.
Alexei Bratuhin
Alexei is senior software engineer at OpenValue. In course of his over 15 years specializing in Java career he collected vast experience in application design, development, operations and support in multiple domains. He is also a passionate contributor to open-source whenever he can - both in his private time and as part of his project work.