.NET Testing Techniques You Didn’t Know You Needed
summary
Covers concrete techniques: mutation testing with Striker inserts hundreds of mutants (example run creates 333 and kills 275) to measure whether tests actually catch bugs; property-based testing with FSCheck generates ~100 randomized cases per property and pushes testing of invariants instead of reimplementing expectations; snapshot testing with Verify captures complex outputs (used on OpenAPI/Swagger files) so diffs show intentional API changes. Also shows Bogus for realistic fakery, seeding for deterministic randomness, and UTC/time abstractions to avoid flakes.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 5:00Why testing matters
- 9:16Incomplete tests and edge cases
- 13:05Randomized testing with Bogus
- 16:14Flaky tests
- 21:33Property-based testing
- 26:07Mars rover kata with FS Check
- 31:49Snapshot testing
- 37:10Testing OpenAPI specs
- 40:00Test effectiveness metrics
- 43:50Mutation testing with Stryker
- 49:33Trust through testing
- 50:35Q&A
