It's the first time I come across this catalog of testing pitfalls.
It's amazing, as I can associate almost all of them to my own errors or to other's work.
It's very useful to put a descriptive semi-humourous name for each of these as facilitate their teaching and our ability to remember them.
This link will definitely find its way in my team's developments standards and guidelines.
"Somehow I missed James Carr's TDD Anti-Patterns late last year. I've perpetuated almost every one at least once. If you're new to testing, browse the list, think about each entry, and watch for it in your own code."