devmate Blog

Although unit testing is a valuable activity for every software development project, it’s also a pain in the ass of every developer who has to deal with it. Why? Because defining, writing, and maintaining your tests over time costs a

Why should we write unit tests? I guess most developers have thought about this already at some stage in their career, and Unit testing is is important. But it’s also hard. That’s why in this article, I argue how you

Short answer: it’s “ship without fear”. Why should we write unit tests? I guess most developers have thought about this already at some stage in their career, and there are a lot of pros and cons of course. In this

You know that you should write unit tests for your code. You know that you should update your tests once you change your code. But you also want to write code to develop new features instead of writing code to

Whereas software testers are the professionals explaining everyone why it is most crucial to exhaustively test every part of your software, it is often difficult for developers to see the benefit of testing. However, especially when it comes to unit

Software Testing is hard. The intention of unit testing is to make it easier through automation. In practice however, unit testing often causes even more pain than software testing. Learn how to cure this pain in this article!   The

Unit testing can be great in theory – but is actually quite burdensome in practice. Writing the same code over and over again instead of creating new functionality. Making sure to adapt a whole bunch of unit tests after each

In this article, you get one single checklist that guides you through the whole unit testing process. By going through all the individual steps of this checklist, you can ensure that you don’t waste any more time on creating unit