Unless the test framework makes you use the same “test” prefix, don’t do it. It messes with separating and identifying unit tests.

Once people understand they actually need to write an assert, this unit tests anti-pattern appears almost immediately. Checking on null is a no-no.

Should we write tests for everything? Absolutely not. Tests that do not help us, cause us more pain while writing and maintaining them are waste. Here’s a common example I see all the time. We have code that translates data from… Continue Reading…