![[The AI Show Episode 143]: ChatGPT Revenue Surge, New AGI Timelines, Amazon’s AI Agent, Claude for Education, Model Context Protocol & LLMs Pass the Turing Test](https://www.marketingaiinstitute.com/hubfs/ep%20143%20cover.png)
![From drop-out to software architect with Jason Lengstorf [Podcast #167]](https://cdn.hashnode.com/res/hashnode/image/upload/v1743796461357/f3d19cd7-e6f5-4d7c-8bfc-eb974bc8da68.png?#)
.jpg?#)
_ArtemisDiana_Alamy.jpg?#)
 (1).webp?#)
-xl.jpg)
![Yes, the Gemini icon is now bigger and brighter on Android [U]](https://i0.wp.com/9to5google.com/wp-content/uploads/sites/4/2025/02/Gemini-on-Galaxy-S25.jpg?resize=1200%2C628&quality=82&strip=all&ssl=1)
![Apple Rushes Five Planes of iPhones to US Ahead of New Tariffs [Report]](https://www.iclarified.com/images/news/96967/96967/96967-640.jpg)
![Apple Vision Pro 2 Allegedly in Production Ahead of 2025 Launch [Rumor]](https://www.iclarified.com/images/news/96965/96965/96965-640.jpg)
Why does testing suck so much?
Why are tests so time consuming to write? And why do they break so easily? And why do they offer no guidance on what went wrong when they do break? This past month I evaluated some of the most common end-to-end (E2E) testing frameworks: Cypress, Playwright, Selenium — and none of them offered a solution to these problems. So I built the next generation of testing tool: testingbee.io. The idea is this: Write automated tests from an end user's perspective. Here is an example of what your test would look like: "Click the searchbar" Type "Docs site" Hit enter You should now be on "docs.ourapp.com" Take these commands and let AI execute them as a human would. And that's how TestingBee works. It fixes all the problems above. Time consuming to write? Not anymore. Just write the steps in pure english. Break easily? Not anymore. Because if the end user flow keeps working then the test will keep working even if the underlying code changes. No guidance to fix tests? Get a direct printout from the AI saying exactly which step failed and why. Edit: I'm looking for early access customers. Reach out and I'll get you an extended free trial! testingbee.io
Why are tests so time consuming to write?
And why do they break so easily?
And why do they offer no guidance on what went wrong when they do break?
This past month I evaluated some of the most common end-to-end (E2E) testing frameworks: Cypress, Playwright, Selenium — and none of them offered a solution to these problems.
So I built the next generation of testing tool: testingbee.io.
The idea is this:
Write automated tests from an end user's perspective.
Here is an example of what your test would look like:
- "Click the searchbar"
- Type "Docs site"
- Hit enter
- You should now be on "docs.ourapp.com"
Take these commands and let AI execute them as a human would. And that's how TestingBee works.
It fixes all the problems above.
Time consuming to write?
Not anymore. Just write the steps in pure english.Break easily?
Not anymore. Because if the end user flow keeps working then the test will keep working even if the underlying code changes.No guidance to fix tests?
Get a direct printout from the AI saying exactly which step failed and why.
Edit: I'm looking for early access customers. Reach out and I'll get you an extended free trial! testingbee.io
