I'm a bit of a cowboy coder and completely skip all but the very top of the testing pyramid. I strictly run E2E tests and albeit slower than other tests, it tes

I'm a bit of a cowboy coder and completely skip all but the very top of the testing pyramid. I strictly run E2E tests and albeit slower than other tests, it tests a much broader spectrum than just a single function. For instance I change the expiration date of a user's subscription, run expire logic, test of this user has received the expected expiration email, this automatically tests the Amazon SES integration, the email template parser and everything in between. Clicking on the expire email call to action button I expect to land on a certain page with elements "missing" and others added, which validates changes in the user's roles. Let's say I swap Amazon SES for Postmark, no new tests have to be written. In my experience this approach works really well for a SaaS like product. It also looks satisfying to see the test suite blast through the site clicking and typing like there is no tomorrow.