Untangle Your Spaghetti Test Code
summary
Test code at this project level is treated as throwaway but causes real maintenance pain so the talk gives concrete fixes: a test data manager that truncates and seeds the database instead of hidden SQL scripts, concise test data builder pattern to reduce boilerplate, centralized act and assert helpers for REST calls, and using approval testing or JSON-equals to make failures obvious. Examples use Java and Spring Boot, show a front-end act helper, and report fewer refactors and far less mock churn when internal APIs change.
AI-written summary · about
chapters (15)
- 0:00Introduction to test code challenges
- 2:10Test code quality importance
- 5:09Arrange Act Assert structure
- 6:37Avoid hidden arrange in setup
- 9:06Test data managers for control
- 12:01Eliminating magic values in tests
- 16:02Shortening arrange with builders
- 19:41Simplifying act with helpers
- 22:14Reducing assert complexity
- 28:32Clear intentions in assertions
- 29:40Problem with inconsistent test names
- 32:51Choosing meaningful test names
- 37:48Balancing conciseness and intent
- 40:53Behavior over specification
- 41:59Cheat sheet and closing
