Test Coverage Myth Busted: Test-to-Code Map and Test Impact Analytics
summary
Sergey challenges common assumptions about test coverage and explains why the often-quoted “magic number 42” is misunderstood. He describes Test-to-Code mapping as the basis for Test Impact Analytics and Test Gap Analysis, and presents a new tool to augment daily QA work and help engineers prioritize tests based on code impact.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 4:31Traditional test problems
- 9:07JavaScript testing myths
- 15:10JavaScript coverage tools
- 22:15Test-to-code mapping benefits
- 28:18JavaScript setup
- 31:50Plugin demo
- 37:55CI/CD test integration
- 44:20Analysis results
- 47:53Conclusion
related talks
48mTest Coverage Myth Busted: Test-to-Code Mapping and Test Impact Analytics
51mDebunking Myths Around Test Coverage
52mTest Impact Analysis. Smarten up your pipeline and reduce t
03mTest coverage
07mHow code coverage can be used and abused to guide testing.
28mUnveiling the Illusion: Why Coverage Alone Is Misleading
39mHow to Talk about Coverage
01h 00mRequirement Coverage: Myth or an Ultimate Goal