<?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/969562d3c0fd49518d0f64aecbddccd6&quot; frameborder=&quot;0&quot; width=&quot;2468&quot; height=&quot;1851&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1851</height><width>2468</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1851</thumbnail_height><thumbnail_width>2468</thumbnail_width><thumbnail_url>https://cdn.loom.com/assets/img/og/slack-protected-video.gif</thumbnail_url><duration>387.06</duration><title>AI-Powered Code Analyzer: Fixing Findings and Test Cases 🤖</title><description>Hey, in this Loom, I&apos;m going to show you how to use our AI-powered code analyzer to fix findings and test cases. First, I&apos;ll generate my app maps by running test cases. Then, I&apos;ll show you how to use the wrench icon to fix problems like deserialization of untrusted data flaw, N plus one query, and failed test cases. Clicking on the wrench sends a prompt to the AI code analyzer, which comes back with a code review comment and a suggested fix. For example, for the deserialization of untrusted data flaw, the suggested fix is to rewrite the code to not use YAML anymore and to use a more secure function called Extract Token. For the N plus one query, the suggested solution is to use the includes method, which triggers a left outer join to fetch all the storage attachments. For the failed test case, the suggestion is to use a flash message to tell the user that they have an invalid activation link and send a redirect instead of just raising an exception. This Loom will help you fix findings and test cases quickly and efficiently.</description></oembed>