Transcript
00:00 Hey, great job on these exercises. Now you know how to get Vetus Browser Remote installed and configured in your project, but also how to migrate your existing GS DOM tests to use the Browser Remote, configure custom browser automation providers, and then use some custom test setups like loading static
00:17 assets like we did with the styles there, and also using multiple test configurations in the same project. I highly encourage you to explore the Vetus documentation because there's always more to learn about component testing and how to use Vetus Browser Remote to make the most out of it. For now, take a quick break and come back so we can go through the next exercise block
00:36 dedicated to the best practices of component-level testing. See you then.