Advanced Testing Techniques: Tips from the trenches
summary
Argues for testing behaviors not implementation, showing a switch from heavy mocks to real objects wired by the production IoC container and subcutaneous tests that skip the brittle UI; recounts a project with 300 UI tests taking 3.5 hours and intermittent failures caused by VM clock drift. Recommends VCR-style recorded HTTP responses, approval tests/snapshots for complex payloads, test-data-builders, try-red-green-refactor (make ugly green then refactor), risk-based testing to set required confidence, and canary/BDI practices to validate in production.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:46UNIT TESTS ARE AWESOME!
- 5:02TESTING BEHAVIOUR IMPLEMENTATION
- 11:05UI TESTS ARE HARD TIME CONSUMING AND BRITTLE
- 14:17TESTING BEHAVIOUR OVER IMPLEMENTATION
- 24:00HOW DO WE TEST BEHAVIOUR?
- 30:01PRAGMATIC TESTING
- 38:26RISK-BASED TESTING
related talks
01h 05mMicrotesting
42mUse testing to Develop Better Software Faster
58mTesting Strategy - New Model, Better Outcomes
44mTesting the untestable - patterns and use cases analysis
28mAdvanced Testing Techniques
29mTesting Applications - How to Do It Better?
37mUnderstanding the successes and the pain points of different testing strategies
40mIntegration Testing from the Trenches - Rebooted