Identifying and Testing Details That Matter Using Automated Tests
summary
Concrete fixes and tools replace vague promises: refactor the Harry Potter bookstore pricing tests to use a shared book price constant and small helper functions so expectations read like a formula and need only one edit when prices change; use xUnit and Gherkin with AutoFixture Fixture.Create or a simple dummy.Any to avoid meaningless literals; compare whole expected vs actual objects instead of multiple asserts; split the caching/rate‑limit scenario into one assertion per test; prefer DAMP over DRY for readable, maintainable tests that actually surface failures.
AI-written summary · about
chapters (9)
- 0:00Automated testing frustrations
- 1:06xUnit testing approach
- 2:08Hardcoded values in tests
- 10:25Dummy values for test data
- 14:02Mapping domain objects
- 17:42Validation test values
- 26:21Refactoring web service tests
- 29:38Readability in Gherkin tests
- 37:44Test readability best practices
related talks
53mThe secret unit testing tools no one ever told you about
48mTesting Should Be Fun
46mAre you writing valuable tests (2025 edition)?
01h 05mMicrotesting
52mxUnit Expanded – Better Testing With xUnit
21mTests That Help you Find Defects Faster
34mBetter Code Through Boring(er) Tests
26mTesting the Tricky Stuff