Derek Zoolander always wants things so big!

Let’s put Zoolander’s advice to the side for now. Are you ready to find out the single best method to help writing unit tests? Here it is:


Whenever possible, split your classes. They should only be doing one thing. If the number of methods is small, then the amount of testing going into it will be a lot easier to manage.

Now a unit test can test just a couple methods. You’re not running tests on something that does too much.

In Clean Code, Uncle Bob Martin writes…

The first rule of functions is that they should be small. The second rule of functions is that they should be smaller than that. Functions should not be 100 lines long. Functions should hardly ever be 20 lines long.

The same could be said of classes. Break it into multiple classes. Use the smaller ones as constructor dependencies in the larger. This will help your testing immensely. It will also prevent you from testing an enormous amount of private methods (because you’re doing too much)!

Don’t be like Zoolander. Small is good!