<?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/de99277c247c4e17890133dea91b4113&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/de99277c247c4e17890133dea91b4113-554a2e641eca2e38.gif</thumbnail_url><duration>1667.167</duration><title>Day 12 - Click Counter - 06 Stress Test</title><description>In this video, I walk you through the stress testing of our tool, focusing on identifying and fixing potential weaknesses in the code. We manually check for errors by providing incorrect and missing values, ensuring that our UI form handles these scenarios gracefully. I also demonstrate how to enhance our tool by adding features like parameter name and category selection, making it more versatile. I encourage you to explore the code further and consider implementing the suggested improvements, especially around error handling and user input management. Overall, I’m pleased with the progress we’ve made, and I look forward to your feedback.</description></oembed>