Why Your Test Suite Sucks

This talk examines common testing pitfalls that can prevent teams from gaining productivity, fewer regressions, and higher code quality. It uses examples involving test-driven development, test doubles, and testing objects and repositories to explain how teams can improve their tests.

Syllabus

Introduction
Dont do this
Not getting the benefits
Different phases of testing
Where do you learn to test
Why move to automated testing
Issue tracking system
Writing the test first
Design implementation first
Test suites still brittle
Testdriven development
Mock queries
Example
Summary
stubs returning stubs
notifying users
train wreck
user object
double or stub
Validate returns
The problem
Double the validator
Design is important
People worry about writing tests
What happens with TDD
TDD is a way to think about your code
TDD is a complicated one
Testing thirdparty code
Testing objects
Testing framework repository
Testing user repository
Double repository
Example of double repository
Cloud API
Interface
Dont Test