You’ve probably seen it coming. I started a series of posts about unit test attributes here, and then went into them in details.
I now morphed the series of posts into a section into the Basic Guidelines chapter. If the other sections I planned are going to be this long, a new order in the Table Of Contents will ensue.
At the time of this writing, I’ve got more than 70 people who purchased the “Everyday Unit Testing” book for free, and even some who paid for it. I want to thank everyone who got a copy, confirming my hypothesis that there’s a need for the book. I hope I want let you down.
I’ve also started getting feedback from people, and some is already integrated in the “Everyday Unit Testing” book. I want to thank Martin Moene, for referring me to the Catch C++ unit testing framework. This is a very cool unit testing framework, and in some cases, better than Google Test framework. The one thing I missed so far is integration with VS unit test runner. I also found a DIY how-to for that, but as I say in the “Everyday Unit Testing” book, smooth IDE integration is very important.
What’s next, you ask?
If you look at the TOC, or the release notes, you’ll see that I’ve added a “Test Economics” chapter. I’ve been thinking a lot lately on the subject, and it’s important enough to be one of the first chapters.
If you disagree, or agree, or want to give feedback, tell me!