Chapter 6

1. A good unit test must be atomic, deterministic, repeatable, and fast.
2. A good unit test must not be inconclusive.
3. Test-driven development.
4. Behavioral-driven development.
5. A small unit of code whose only purpose is to test a single unit of code that only does one thing.
6. A fake object used by the unit test to test the public methods and properties of a real object, but without testing the method or property dependencies.
7. A fake object is the same as a mock object.
8. MSTest, NUnit, and xUnit.

9. Rhino Mocks and Moq.
10. SpecFlow.
11. Unnecessary comments, dead code, and redundant tests.