1.
Testing Antipatterns <ul><li>Matt Robinson </li></ul><ul><li>Puppet Labs </li></ul>

2.
Anti - What?

3.
Antipattern ( Dark Pattern ): <ul><li>A pattern that is commonly used but is ineffective and/or counterproductive </li></ul>

5.
Who has an extensive test suite?

6.
Who feels like they should test more?

7.
Who dislikes, even dreads, writing tests?

8.
Testing Can Be Fun Text Text Text Text http://xkcd.com/583/

9.
For example:

10.
Red Green TDD Addiction

11.
Testing Framework Games (although these can be a distraction) (although these can be a distraction)

12.
Not looking like an idiot - that’s fun right?

13.
Why Automated Testing? <ul><li>Prevents regressions </li></ul><ul><li>Improves confidence </li></ul><ul><li>Documents requirements </li></ul><ul><li>Catches errors before codes ships </li></ul><ul><li>You fill in the blank _________ </li></ul>

14.
Overheard Reasons Not to Test <ul><li>Don’t trust the tests </li></ul><ul><li>Who tests the tests? Quis custodiet ipsos custodes? </li></ul><ul><li>Makes refactoring harder </li></ul><ul><li>Not enough return on investment (ROI) </li></ul><ul><li>Too hard and/or time consuming </li></ul>

15.
Antipatterns that have bitten me the most

16.
Not Running Tests Often Enough

17.
If it’s Hard and Important Do it More Often

18.
testing, deploying, releasing, exercising, meditating, writing, public speaking

19.
How Often? <ul><li>Before deployment or release </li></ul><ul><li>After every commit: CI (Continuous Integration) - Jenkins, Cruise Control, BuildBot, Cerebrus, CI Joe </li></ul><ul><li>Before every commit (or push): discipline, git hooks </li></ul><ul><li>Every save: autotest, watchr </li></ul>

20.
Not Fixing Broken Tests Before Committing New Code

21.
The Slowpoke

22.
How Slow Is Too Slow?

23.
Unit Test Suite Took 8 Hours to Run - On One Project

24.
Single Test Took 2 Minutes to Start

25.
So slow that rewriting it in PHP would make it faster

26.
How to Get Faster <ul><li>Make your implementation code faster </li></ul><ul><li>Run your tests in parallel </li></ul><ul><li>Optimize your tests (new framework, trick garbage collector, rewrite culprits) </li></ul><ul><li>Mark some tests as slow and only run them occasionally </li></ul>

27.
The Mockery

28.
Why mock when the real things will do?

29.
Testing at the Wrong Level

30.
unit, smoke, functional, integration, acceptance

31.
Success Against All Odds (test never fails) (test never fails)

33.
Testing Implementation Instead of Behavior

34.
Testing Implementation

35.
Testing Behavior

36.
Order Dependent Failures

37.
You’ve got too much global state

38.
Excessive Setup

39.
What are we testing again?

40.
<ul><li>The Dodger - Never tests desired behavior </li></ul><ul><li>The Stranger - Misplaced tests </li></ul><ul><li>Local Hero - Worked on my dev box </li></ul><ul><li>Generous Leftovers - Fills your hard drive </li></ul><ul><li>The Giant - You may have a God object </li></ul><ul><li>The Loudmouth - Spams your test logs </li></ul>Other Antipatterns

41.
Summary

42.
Avoid Antipatterns and Testing Can Be Fun

43.
Links <ul><li>http://blog.james-carr.org/2006/11/03/tdd-anti-patterns/ </li></ul><ul><li>http://jasonrudolph.com/blog/testing-anti-patterns-how-to-fail-with-100-test-coverage/ </li></ul><ul><li>http://blog.rubybestpractices.com/posts/gregory/034-issue-5-testing-antipatterns.html </li></ul><ul><li>http://c2.com/cgi/wiki?AntiPatternsCatalog </li></ul><ul><li>http://martinfowler.com/articles/mocksArentStubs.html </li></ul>