Test Coverage Myth Busted: Test-to-Code Mapping and Test Impact Analytics

on YouTube ↗48m

" summary

Explains a practical approach to test coverage that maps each test to exact methods and lines using source maps and Istanbul instrumentation, arguing the overall percentage is misleading. Presents the open-source tool drill for js, which collects coverage from browser and server runs, links manual and automated executions, and computes per-method risk scores so CI pipelines can prioritize and run only tests impacted by code changes.

AI-written summary · about

" chapters (9)

1. 0:00Introduction
2. 2:52Test coverage problems
3. 7:52How many tests enough
4. 11:27Testing risks confidence
5. 16:44Test-to-code mapping
6. 21:17How Drill for Java works
7. 25:19Drill for Java demo
8. 34:39Integration test frameworks
9. 37:28Q&A

" related talks

• 49mTest Coverage Myth Busted: Test-to-Code Map and Test Impact AnalyticsSergey Pirogov · Selenium Camp 2020
• 49mTest-to-Code Mapping, Code Coverage by Automated and Manual Tests!Dmitriy Gumenyuk · QA Fest 2019
• 52mTest Impact Analysis. Smarten up your pipeline and reduce tBart Szulc · DelEx Conf 2019
• 03mTest coverageArvid Norberg · CppCon 2018
• 51mDebunking Myths Around Test CoverageSergey Pirogov · QA fwdays'20 online conference
• 49mTest Coverage VisualizationArtem Eroshenko · Selenium Camp 2020
• 07mHow code coverage can be used and abused to guide testing.Maurício Aniche · It Will Never Work in Theory (Online, April 2022)
• 10m99% is not enough - full test coverage and why it's awesomeIsaac Z. Schlueter · Assert(js) 2019