Measure End to End Tests Coverage
summary
Shows how to build an instrumented binary by compiling tests with go test -c and a custom TestMain to produce coverprofiles, then merge profiles and view reports with go tool cover. A running integration coverage binary records which code paths execute so staging or sampled production traffic reveals dead code; example numbers: unit-only 21%, merged coverage 92%, single integration run 83% then drops to 78% after a small optimization. Sets a practical 75% threshold and notes coverage is noisy but catches real bugs.
AI-written summary · about
chapters (8)
- 0:00Introduction to E2E test coverage
- 2:25Demo of calculation API service
- 10:30Coverage drop after code change
- 13:33Summary and metrics approach
- 17:05Merging coverage reports
- 19:41Detecting dead code with coverage
- 23:30Validating test correctness
- 28:13Test pyramid and coverage rules
related talks
07mGenerating Coverage with System Test
43mTest coverage in Go, the whole package
19mTesting Your Tests With Code Coverage
44mGo Testing By Example
03mTest coverage
42mBoosting Test Coverage for Microservices
40mBoosting test coverage for microservices
52mCross-Platform Unit Testing and Code Coverage with Coverlet