Transcript
00:00 Once you put the setup blocks in place, your end to end test becomes not that different from a component test. And that's great because it means that all the things and best practices of component testing that you already know still apply in your end to end tests. The things like writing accessibility first locators or acting as the user would, or asserting on the intention, the things you expect to happen in the UI. That is a great reminder that all these testing levels are not separate disconnected universes, but instead different edges of the same thing automated testing. And the only thing that really changes is how much you zoomed in or zoomed out on your system.
00:36 When talking about end to end testing, of course, you pretty much zoomed out to involve all the parts of your app. But despite that, you still want to focus on testing isolated behaviors or user journeys, and there are a lot of things that may come in the way just due to the sheer amount of the moving parts involved. This is why the test setup is extremely important in end to end tests, because it will allow you to reproduce those scenarios reliably while simultaneously offloading the complexity introduced by your app. So in this exercise block, I wanted us to focus on the things to help you elevate your test setup from preparing test data to mocking the network, and also mentioning a few quality of life improvements such as writing end to end tests faster by recording the browser. We've got a lot to cover, so let's go.
