Clean Code

T9:
Tests Should Be Fast
A slow test is a test that won’t get run. When things get tight, it’s the slow tests that will be
dropped from the suite. So 
do what you must 
to keep your tests fast.
Conclusion
This list of heuristics and smells could hardly be said to be complete. Indeed, I’m not sure
that such a list can 
ever
be complete. But perhaps completeness should not be the goal,
because what this list 
does
do is imply a value system. 
Indeed, that value system has been the goal, and the topic, of this book. Clean code is
not written by following a set of rules. You don’t become a software craftsman by learn-
ing a list of heuristics. Professionalism and craftsmanship come from values that drive
disciplines.

---

315
Bibliography
Bibliography
[Refactoring]:
Refactoring: Improving the Design of Existing Code
, Martin Fowler et al.,
Addison-Wesley, 1999. 
[PRAG]:
The Pragmatic Programmer
, Andrew Hunt, Dave Thomas, Addison-Wesley,
2000.
[GOF]:
Design Patterns: Elements of Reusable Object Oriented Software
, Gamma et al.,
Addison-Wesley, 1996.
[Beck97]:
Smalltalk Best Practice Patterns
, Kent Beck, Prentice Hall, 1997.
[Beck07]:
Implementation Patterns
, Kent Beck, Addison-Wesley, 2008.
[PPP]:
Agile Software Development: Principles, Patterns, and Practices
, Robert C. Martin,
Prentice Hall, 2002.
[DDD]:
Domain Driven Design
, Eric Evans, Addison-Wesley, 2003.

---

This page intentionally left blank 

---

317