Launch HN: DeploySentinel (YC S22) – End-to-end tests that don't flake
While what you have made looks cool it seems like you are leaving out a lot of what is at the basis of many hard to maintain flaky e2e tests: a fundamental wrong approach to testing resulting in too many tests in the development process where they simply do not belong.<p>The [test automation pyramid](<a href="https:&#x2F;&#x2F;www.google.com&#x2F;search?q=test+automation+pyramid&amp;sxsrf=ALiCzsZWChhGCToG0fDx6OqsK3MJbLJKug:1659526078421&amp;source=lnms&amp;tbm=isch&amp;sa=X&amp;ved=2ahUKEwiJ8pizyKr5AhXbnP0HHWc-AXwQ_AUoAXoECAEQAw&amp;cshid=1659526095972504&amp;biw=1920&amp;bih=957" rel="nofollow">https:&#x2F;&#x2F;www.google.com&#x2F;search?q=test+automation+pyramid&amp;sxsr...</a>) or even the [testing trophy](<a href="https:&#x2F;&#x2F;twitter.com&#x2F;kentcdodds&#x2F;status&#x2F;960723172591992832" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;kentcdodds&#x2F;status&#x2F;960723172591992832</a>) doe exist with very good reason.<p>The earlier you can write your tests the easier it is to break them up in the relevant individual functionality without tests being flaky. Now you can argue the merits of Unit tests, hence the testing trophy also being a thing. But the fact of the matter is that 90% of the time e2e tests are flaky because teams try to test things in them that shouldn&#x27;t be tested at that level.<p>Having said that, the ability to inspect the DOM, network requests, etc at various places in history is a very neat ability.