<?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/e88c3fb832b54f7fafc3dde05ae50470&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/e88c3fb832b54f7fafc3dde05ae50470-9a9d125344f9e745.gif</thumbnail_url><duration>275.94</duration><title>Testing Rhombus AI Pipeline, UI to Data Validation</title><description>Hi, I am Ishan, and this Loom walkthrough covers three parts of the Rhombus AI take home exercise. For UI automation, I used Playwright with JavaScript to sign in via saved session state, create a project, upload the CSV, run the pipeline, wait up to two minutes for the run button, and assert success with a five minute timeout. For API testing, I used a black box approach by inspecting network calls and wrote four tests, two positive and two negative, including cases for missing auth and a fake project ID. For data validation, I compared input and output CSVs with row count, schema, casing, date formats, consistency, and whitespace checks, and I found a real bug where extra whitespace remained around the salary value in row 8. I did not request any action from viewers.</description></oembed>