The Art of Unit Testing, Second Edition: with examples in C#

“Red-Green-Refactor,” meaning that you start with a failing test, then pass it, and then make your code readable and more maintainable.

Here are the three parts of the test method name: UnitOfWorkName —The name of the method or group of methods or classes you’re testing. Scenario —The conditions under which the unit is tested, such as “bad login” or “invalid user” or “good password.” You could describe the parameters being sent to the public method or the initial state of the system when the unit of work is invoked such as “system out of memory” or “no users exist” or “user already exists.” ExpectedBehavior —What you expect the tested method to do under the specified conditions. This could be one of three possibilities: return a value as a result (a real value, or an exception), change the state of the system as a result (like adding a new user to the system, so the system behaves differently on the next login), or call a third-party system as a result (like an external web service).

For each unit of work, create a test method with the following name: [UnitOfWorkName]_[ScenarioUnderTest]_[Expect edBehavior].