As an SRE, I was frustrated by the lack of e2e test coverage causing incidents and keeping me up at night :(
I’ve noticed that e2e testing has behind modern development practices. Many teams skip it because the tests are hard to create or maintain.
With more teams using AI coding agents, code gets shipped quickly and maintenance-heavy test suites keep blocking merges or breaking production due to poor coverage.
I built blastproof to solve this problem in my own workflow. It runs tests written in YAML using plain English and doesn't rely on CSS selectors or XPath.
It has some limitations, but the README is quite honest about them.
Hi HN! I’m Heitor.
As an SRE, I was frustrated by the lack of e2e test coverage causing incidents and keeping me up at night :(
I’ve noticed that e2e testing has behind modern development practices. Many teams skip it because the tests are hard to create or maintain.
With more teams using AI coding agents, code gets shipped quickly and maintenance-heavy test suites keep blocking merges or breaking production due to poor coverage.
I built blastproof to solve this problem in my own workflow. It runs tests written in YAML using plain English and doesn't rely on CSS selectors or XPath.
It has some limitations, but the README is quite honest about them.
[flagged]