Point and Shoot Testing

It's an often brought up tool within testing circles. In fact, Playwright themselves advertise the tool with the headline "Playwright enables reliable end-to-end testing for modern web apps". And for a lot of people that get to the point of stability within their web app, I'm sure having end-to-end testing may be useful. In my case, I find myself often iterating on my web app's designs until I get to the place I like them, so a UI test seems like it would be counterintuitive. However, with the age of end-to-end testing frameworks comes the ability to rapidly snapshot the state of your application. And this ability requires no tests or complex state machines to execute on. It's just like the classic camera saying, just "Point and Shoot!". However, with this ability comes an almost unbelievable productivity boost when working on web apps targeting multiple screen sizes. Especially in the age of agents. You might be wondering, what do agents have to do with this? Well, in truth, not so much, because many of these benefits extend to manual programming too. So let's get to it then, what are the benefits? Well, as soon as you make any UI change, you have the ability to run a 2s script and instantly know which UI scenarios changed, across many different screen sizes, instantly. No longer is there the requirement to fumble with browser dev tools to shrink the screen. No longer is there the need to have a phone and tablet to test your changes with. It's now a simple command run, and instantly changes across every single screen size and scenario you care about are shown. This is especially handy when these pictures are put into CI because you can get an easy indicator of which UI scenarios did and didn't change, which before having this seemed like a nice benefit, but after having used this for several design changes, is a lifechanger. Ultimately, you just can't go wrong with more visibility into your app.