<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/37dc0793d5a24404be6ca066e3785245&quot; frameborder=&quot;0&quot; width=&quot;1114&quot; height=&quot;835&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>835</height><width>1114</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>835</thumbnail_height><thumbnail_width>1114</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/37dc0793d5a24404be6ca066e3785245-6dcedd793384d006.gif</thumbnail_url><duration>236.416</duration><title>testcode.ai finding real world regressing code bugs</title><description>In this video, I discuss how high code coverage doesn&apos;t guarantee the absence of regression bugs, using a real-world example from the Apache Common Language Library. I demonstrate how our tool, Testcode, can identify critical mutations that may go undetected even with good coverage. It&apos;s crucial for developers to understand that mutation testing can reveal potential gaps in their unit tests. I encourage you to consider how Testcode can enhance your testing strategy.</description></oembed>