E2E tests that survive moving a button

At one point I merged what I thought was a harmless UI change. I moved a button. Dozens of E2E tests failed overnight, and none of them had found a real bug. The tests weren't catching problems, they were just reacting to selectors that had shifted a few pixels.

That's the thing about traditional automated tests. They're too brittle to survive a real product that changes every day. A suite that's supposed to give you confidence starts doing the opposite.

So I built TestingBee. Instead of writing test scripts, you describe what a user should be able to accomplish in plain English. The AI figures out how to do it against your actual app. Since it works from intent instead of selectors, a UI tweak doesn't blow up your suite.

The nice side effect is that anyone can write tests. PMs, designers, support. If you can describe the flow, you can test it.

You can try it at testingbee.io, and I wrote more about the thinking behind it in Introducing TestingBee.io.