The necessity of unit testing ceased to be the subject of discussion lately: the real-life practice has proved, that unit tests are essential for a stable product. But speaking about the necessity of writing unit tests, authors often forget to explain how to do this. At the same time, many developers don’t give pride of place to unit tests as a part of their job. The common approach is when developers simply create a test project using a basic testing framework only and then use this project to solve the same tasks again and again. Such an approach is not time efficient because testing consumes more time than coding. The outcome is predictable and always the same: developers refuse writing tests to meet the next strict deadline, or testing turns into a tedious ritual.