And what about unit and functional tests?

Except for a short note in Chapter 1, Introduction to Automated Testing, and mentioning a couple of MS test codeunits that apparently hold unit tests, we haven't paid any attention to the concept of unit tests so far. In this chapter, however, discussing the need for a test plan entailing all tests verifying the behavior of the feature, it makes a lot of sense to pick up that gauntlet laying in sight: what about unit tests?

My short answer to this question is: please, go ahead and implement them.

But quite obviously that might not be the answer you're looking for. So, let me work this out a little bit more in a number of bullet points:

• In my humble opinion, unit tests are the sole responsibility of developers. They build them to check the validity of the atomic units that altogether make up a feature. These atomic units are the procedures and methods they have created to implement a feature. As such, unit tests are not...