Talk about Design Patterns general reusable solution to a commonly occurring problem
Realized while writing this talk that I was focusing on what pissed me off and made me not want to talk about it. Should be humor in testing.
Red failing Green passing
Not really an antipattern since it’s really only solving being lazy
CI essentially glorified cron job
The Joel Test #5: Fix bugs before writing new code Mention Lava Lamps
Martin Fowler Mocks aren't Stubs. Never met a mockist whose tests I liked. Not mocking means mini integration tests. Possibly controversial. When to mock: code you don't control - file system, web server, external libraries like ssl
Too much mocking might indicate this
Everyone has their own terms
Test Driven Development prevents this
Behaviour Driven Development is a larger term with more meaning
These are annoying but can’t be ignored. How to find these failures - binary search.
Testing antipatterns can indicate antipatterns in your implementation code