<?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/a492b2efb7164acfaa810d93ff09c43f&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/a492b2efb7164acfaa810d93ff09c43f-cb06c20f5d86579e.gif</thumbnail_url><duration>71.743</duration><title>Implementing a Dual Stack Mono Repo for Automation Testing</title><description>In this video, I present my technical solution for the Sostemo automation task, where I&apos;ve implemented a dual stack mono repo using Playwright with TypeScript and Selenium with Java. My goal was to establish a symmetrical architecture that separates the core library from the functional test suite to maximize reusability across different teams. I demonstrate how I leveraged custom fixtures in Playwright to enhance readability and focus on business logic by injecting page objects directly. Additionally, I abstracted all credentials into a user.ts data module to promote a data-driven approach. I encourage you to review the implementation and consider how these practices can be applied to our projects.</description></oembed>