The document discusses various code smells and anti-patterns that can occur when writing and testing code. It lists 14 different code smells and anti-patterns that indicate issues like dependencies between modules, overuse of inheritance or mocking, tests that are too high or low-level, and inconsistencies. The document is written by Simon Stewart and provides links to related images and discusses how testing may fall off when projects become difficult.

1. The Stinky Code Project
Simon Stewart (shs@google.com)
@shs96c

2. Data Envy

3. Breaking the Law (of Demeter)

4. The Evil Singleton

5. Static Cling

6. Mocking Too Far

7. Too Many Mocks

8. Tests at Too High a Level

9. Tests at Too Low a Level

10. Fat Constructors

11. Deep Inheritance

12. Obscure Intent

13. Polynaming

14. Single Layer of Defence

15. Test Code is Disposable

16. Mumpsimus
http://www.flickr.com/photos/deepblue66/132439533/

17. When the Going Gets Tough (the
Tough Stop Testing)

18. Inconsistency
http://www.flickr.com/photos/31284576@N06/3105146919/

19. Fin