Why Your Test Suite Sucks

Explore a comprehensive conference talk that delves into common pitfalls of test-driven development (TDD) and how to overcome them. Learn why teams often struggle to reap the promised benefits of TDD despite having seemingly healthy test suites. Discover the different phases of testing, understand the motivations behind automated testing, and gain insights into writing effective tests. Examine practical examples of mocking queries, handling stubs, and dealing with complex object interactions. Uncover the importance of proper design in testing and how TDD influences code thinking. Address concerns about writing tests, testing third-party code, and working with repositories. Gain valuable knowledge to improve your test suite and maximize the benefits of TDD in your development process.

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