Sorry my response was geared more towards what I hope the future of e2e (and bleeding into integration) testing could entail, independent of what we manage to a

Sorry my response was geared more towards what I hope the future of e2e (and bleeding into integration) testing could entail, independent of what we manage to accomplish - as opposed to trying to sell our product. I do get excited thinking about where testing can improve - with the end goal that developers get to ship reliable apps for their users with less frustration of testing along the way. Our product is very much just a minuscule fraction of our way there with our current iteration. I also totally agree - e2e tests deserve better tooling to debug, and that alone we've found quite compelling of a product to be working on already, and I appreciate you find it cool as well :D With regards to picking the right level of testing - I think there's a few km long rabbit hole to go down with that one, and I totally admit I hold strong beliefs that are different from most people in testing today. I agree though - there's always going to be a different preferred tool for different problems. It'd be pretty wild to expect e2e testing to accomplish the bulk of it! That being said, I think if e2e tests were better in a few dimensions, developers might find it useful for more use cases than they do today (some teams we talk to want to do more e2e tests but find the shortfalls as a real barrier to justify the investment).