Checking Unit Tests: Key Signs of Failing Approaches
summary
Covers common anti-patterns in unit testing, showing how to recognize failing test design at a glance and how to improve test code. Uses Java examples and discusses how to communicate suggested improvements to developers.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:15Why tests aren't always useful
- 4:28Testers and unit tests
- 8:21Visual test review
- 15:04Good test structure
- 24:03Bad tests and consequences
- 26:53Rules for effective tests
- 34:55Test design timing
- 41:56Selling tests to business
- 43:21Cargo cult testing
- 45:49Test-writing culture
- 47:16Testers and scenario prep
- 48:42Unit tests and automation
- 50:49Private methods and testing
related talks
55mUnit Testing Like a Pro - Towards a Testable Design
12mThe Tester’s Guide - 6 Bad Habits You Must Break
43mGot a #bug? Your Unit Tests Are Not Properly Designed
40mA Tale of Unit Tests, Code Coverage and Code Design
48mEffective Unit Testing
45mTesting the untestable PART II – patterns, use cases and practices
01h 01mHow to (Not) Use Testers Properly
36mLiving on crotches or UI Automation antipatterns