Test-to-Code Mapping, Code Coverage by Automated and Manual Tests!
summary
An open-source tool called drill instruments the JVM at the bytecode level (without changing application code) to map tests to the exact methods they touch, making coverage actionable. It shows automated and manual test sessions recorded in real time, integrates with ReportPortal, collects SQL/exception context, and can highlight methods added or changed in a build diff (example: 2060 -> 2075 methods with 7 modified, 18 new, 3 removed) so you know which tests to rerun when new methods have zero coverage.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:17Code coverage problems
- 8:59Test-to-code mapping
- 15:42Drill4J overview
- 20:26Drill4J demo
- 33:19Technical details
- 38:37Future development
- 40:01Q&A
related talks
53mTest Gap Analysis and Regression Suite Minimization with Drill4J
48mTest Coverage Myth Busted: Test-to-Code Mapping and Test Impact Analytics
49mTest Coverage Visualization
50mCode Coverage Instrumentation
01h 00mTest Impact Analysis for Android & JVM
35mSmarten Up Your Pipeline and Reduce Test Execution Time｜
49mTest Coverage Myth Busted: Test-to-Code Map and Test Impact Analytics
46mJava, Code Coverage & Their Best Friend: Bytecode