> it’s about building better software faster Great. Go over in that corner and argue with the other testers and some managers about defining "better" while the

> it’s about building better software faster Great. Go over in that corner and argue with the other testers and some managers about defining "better" while the rest of us get some work done. > strong emphasis on unit tests, and while they have their place, let’s not forget about a category of tests that I consider much more valuable when it comes to testing complex web application user interfaces: End-to-End First, testing UI doesn't mean the tests have to be End-to-End(E2E). Second, I have the opposite experience, where teams seem to want test devs to write slow, brittle E2E tests that require maintaining fragile environments that often need to cross-coordinate among many repos deploying to it (plus any manual changes that always seem to happen). I see very little emphasis on unit tests. And I see almost none on contract tests, the fast way to break E2E tests into grok-able pieces that can run on every push (just like unit tests). > let’s shift our focus from output to outcome I don't really see that a focus on E2E tests outcomes. I just see that as slow, brittle, high-maintenance, and something requiring an environment (thus not running the tests on every push - even slower feedback). Maybe try to focus on fast, meaningful feedback instead?