Seek Nuance

Sometimes you don’t write unit tests. Your reason for not doing so always falls into one of two categories.

Complexity

The code you just wrote would be so much easier to test using system-level testing. For example…

• The setup and teardown would be 10x the test code.
• There’s too much interaction with multiple data stores or third-party vendors.
• Your dev boxes or CI server don’t all have the necessary technology installed.

These are rational reasons to not write unit tests for new code. You’re fine.

Simplicity

But sometimes you don’t write unit tests because the code you just wrote is so darn obvious.

It’s really simple. It’s straightforward. It’s nearly trivial. Why both writing unit tests for it?

Well, I’ll tell you why you should test it. In fact I’ll give you three reasons.
Read more…