How to unit test an abstract class? Or a whole class hierarchy that depends on that abstract class? Let’s see.

In this post, we’ll make a deep dive into the DRY and DAMP principles and will talk about the false dichotomy around them.

Need to change validation rules but have pre-existing data that doesn’t follow the new rules? In this post, we’ll talk about how to do that properly.

The use of mocks in unit testing is a controversial topic (maybe less so now than several years ago). I remember how, throughout my programming career, I went from mocking almost every dependency, to the "no-mocks" policy, and then to "only mock external dependencies".

None of this practices are good enough. In this article, I’ll show you which dependencies to mock, and which to use as is in your tests.

In this article, we’ll review the types of unit testing dependencies. This is more of a reference article, to which I’ll be referring in future posts. Still, this topic is important for establishing the common vocabulary.

This article is about 3 things that can make or break any software project.

In this post, we’ll talk about whether or not you should use assertion messages in tests.

In this post, we’ll discuss an interesting question about whether the concepts of Entity and Value Object are the same.

Combining bulk operations with Domain-Driven Design is a tough problem. In this article, we’ll look at why that is so and discuss ways to marry the two.