David’s Reviews > Developer Testing: Building Quality into Software (Addison-Wesley Signature Series > Status Update

Just talking about mocking frameworks (java & c#). Similar to gmock for c++.

There were lots of suggestions about naming tests with nomenclature for the various types, then info about matchers and their differences between implementations.

chapters 4 & 5 on testability from a dev's perspective and programming by contract. One interesting note was about the level of abstraction of the language used modifying how much testing at the dev level needs to be done, e.g. if the language (like Ruby) takes care of exceptions for out of range arguments, no code has to be written for such cases.

Terminology clarifications in chapter 3.

Intro topics so far. Devs should test their code, preferably in a way that can be repeated automatically.