Below you will find pages that utilize the taxonomy term “TDD”
Talks
Sugar rush of Kotlin for your tests
Why do teams prefer Kotlin for their tests, even when their production code stays in Java?
Learn how Kotlin’s syntax helps keep tests clean, expressive and concise.
Talks
WIP: External domain context with Ktor and Kotlin DSL for expressive and resilient testing
Learn how to build meaningful functional tests in isolation. The highlights of this technique are the minimal deviation from the production configuration or code, and very limited use of mocking. Thanks to higher tier positioning on the testing pyramid, the tests written with this technique are quite implementation-agnostic, and excel in supporting structural refactorings or high-level documentation of the component behavior.
Talks
WIP – Mocks: is more always better?
Mocking and stubbing are, without any doubt, important techniques for a modern software developer to master. But can there be too much of the mocking goodness?
Posts
Spring @Transactional programmatically
Beware: this post is WIP.
An an enterprise developer, it’s easy to get used to the conveniences of Spring (Boot) so much that it becomes an issue on itself. Take @Transactional. Arguably, one of the few core features of Spring that does make us more productive in development. But at times it can be slightly inconvenient to rely solely on annotation for transaction boundary setup:
It might not be desireable to have a database transaction open throughout the whole request processing, e.
Posts
Java Integration Tests v Spring Context – when less is more
When doing integration testing within a Spring (Boot) based project, we tend to use some sort of Spring context. Setting it up isn’t free. Careless tests composition can lead to much time wasted on re-creating those contexts, and will make running tests painfully long very quickly. There are simple techniques of keeping this overhead to the minimum. Ideally – start only one test context for the whole run.