Hey everyone I built CueTest because end-to-end testing often becomes a project of its own. Writing the first test is manageable. The real pain starts later—selectors change, tests become flaky, failures are hard to understand, and developers end up spending more time maintaining automation than testing the product. I wanted something simpler: describe the user journey in plain English, run it in a real browser, watch what happens live, and get a clear explanation when something fails. That idea became CueTest. The platform has evolved from basic AI-driven browser execution into a more complete testing workflow with reusable test flows, parallel execution, shared browser sessions, visual testing, limited self-healing, CI/CD triggers, screenshots, logs, and AI-powered failure analysis. CueTest is built for solo developers, startups, agencies, and teams that want useful end-to-end coverage without maintaining a large traditional test suite. I’d really appreciate feedback—especially on the test creation experience, execution reliability, and whether the failure reports give you enough information to act quickly.

CueTest

E2E Testing simplified to just plain english

E2E Testing simplified to just plain english