{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/0702e2e7ee4d459c8e1d044396bba906\" frameborder=\"0\" width=\"1678\" height=\"1258\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1258,"width":1678,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1258,"thumbnail_width":1678,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/0702e2e7ee4d459c8e1d044396bba906-9c11d43f13354dd0.gif","duration":110.043,"title":"Undercover Intro","description":"In this video, I introduce Undercover, a tool I developed to address the issue of shipping untested code, even when coverage appears high. Unlike traditional percentage-based coverage metrics, Undercover identifies every untested method, block, and branch, providing detailed annotations for each. I encourage you to run Undercover locally to verify coverage before committing your code, and to use it in your pull requests to highlight missing tests. For teams, our GitHub app can be configured to match your workflow, ensuring that missing coverage is flagged appropriately. To get started, simply type \"gem install undercover\" in your terminal."}