A talk given at BarCamp Manchester on 2nd March 2008

1. Testing Times
Drive your Development and Trust your Code.

2. Rule #1
Test Your Code
• Unit Tests - you have them, right?
• Why? Confidence & Contract
• Multi-developer Friendly
• Backward Compatibility / API Compliance
• Accountability (halt scope creep!)

3. Standard Iterations
1. Specification
2. Implementation to Spec
3. Testing
4. Release

4. TDD Iterations
1. Specification
2. Testing
3. Implementation to Tests
4. Release

5. Rule #2
Run Your Tests
• 3 types of tests
• Unit / Integration / Acceptance
• Unit tests should be very fast run every build
• Integration tests should be run before commit
(You use version control, right?)
• Acceptance tests are hard to automate

6. Cruise Control

7. Bamboo

8. Rule #3
Get Covered
• Measure Code Coverage
• Tests (EMMA, Cobertura, Clover)
• Peer Review (Crucible)
• Identify & Repair Unacceptable Risk

9. Crucible

10. TDD Example
or Discussion?