{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/683390a95646405aba2c9c6daa528023\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/683390a95646405aba2c9c6daa528023-e2c02dc4572ee11b.gif","duration":625.458,"title":"Day 02 -  DoorSwing - 05 Stress Test","description":"In this video, I walk you through the stress testing process for our tool to identify and fix potential issues before users encounter them. We discuss the importance of checking for changes in the API, ensuring parameters are correctly handled, and verifying the existence of shared parameters across projects. I demonstrate how to use AI to analyze the code and highlight areas prone to failure, emphasizing the need for robust error handling. I encourage you to implement these checks in your own tools to enhance reliability. Finally, I reflect on the concepts we've applied and how they can be useful for future projects."}