What’s Your Test Design Debt? Avoid the Inevitable!
summary
Defines test design debt as the implied cost of fixing quick and dirty tests and maps ISO 25010 maintainability (modularity, reusability, analyzability, modifiability, testability) onto test cases. Shows concrete fixes: run reviews, measure coverage and traceability, use a glossary, separate navigation from tests, use preconditions, parameters and checklists, avoid “or” and fuzzy terms, stop putting actions in expected results, plan test design and pick a matching test management tool. Lists three choices for changes and three key design aspects.
AI-written summary · about
chapters (17)
- 0:00Test design debt intro
- 1:09Requirements change impact
- 3:17Handling requirement changes
- 5:47Test case changes causes
- 8:41Test design debt definition
- 9:23Maintainability principles
- 13:16Analyzability and modifiability
- 16:27Testability and reviews
- 17:11Quality criteria for tests
- 19:59Tips for maintainable tests
- 22:29Do you need a test case?
- 24:55Divide and conquer
- 27:44Granny test cases
- 31:39Unique test pieces
- 33:01Clear test case language
- 36:58Practical maintainability tips
- 39:47Test design balance
related talks
41mFixing Design with Tests
28mDesign for Testability
08m"Better Ideas at Test Design"
42mDesign Driven Concepts for Automated Testing
41mExits on the (QA) Highway to Hell
33mTest Design for Dummies
28mYour Testing Strategy is broken - lets fix it!
18mTest Design Techniques, or How to Properly Cover an Application with Tests