CueTest

Plain-language browser E2E tests with verified, traceable results

Intermediate API
Screenshot of CueTest, Plain-language browser E2E tests with verified, traceable results

What is CueTest?

CueTest is a coding tool. CueTest runs end-to-end browser tests written in plain English on hosted browsers, verifies each expected result independently, and returns traces, screenshots and reports. It plugs into CI pipelines and starts free.

CueTest is a hosted platform for end-to-end browser testing in which tests are written as ordinary sentences instead of selector-based code. Each test is a sequence of ordered steps, and every step carries one instruction and one expected result. Teams can reuse step groups, run a selected range, or execute a whole project in order, with credentials referenced through environment placeholders rather than typed into steps. Execution happens in real hosted browsers, with one browser context kept for the full run. An AI agent performs each step inside a fresh, bounded context, and a separate verifier then checks the expected result against the live page. That split matters: a step passes only when the page confirms the outcome, not when the model claims it finished. Successful interactions are saved as a replay plan. Later runs try that deterministic plan first and call the AI only when the saved path no longer proves the result, which is the healing behavior that keeps maintenance low when an interface changes. Every run returns evidence: a trace, screenshots, a report, and the exact failed step. Runs can be triggered from GitHub Actions, GitLab CI, or any pipeline able to call an API, so the output can gate a release. The homepage also offers a no-signup hosted trial run against a public URL, limited to one run per browser window and three minutes. The audience is fast-moving SaaS teams, lean engineering-led QA groups, and teams already running Playwright or Cypress who want adaptive coverage for the journeys that change most, such as checkout, onboarding and permissions. It is positioned as a complement to coded suites rather than a full replacement. Pricing is based on browser minutes and AI resolutions instead of the number of saved steps, which sets it apart from tools that charge per test. Alternatives include maintaining Playwright or Cypress scripts by hand or using other AI testing agents, and CueTest's distinguishing choices are independent verification and replay-first execution.

How do you use CueTest?

  1. 1Try the hosted demo
    Enter a public URL and a one-sentence journey in the trial box on the homepage. No account is needed, and a run lasts up to three minutes.
    CueTest — Try the hosted demo
  2. 2Create a free account
    Sign up for the Free plan, which needs no card and includes 30 browser minutes each month.
    CueTest — Create a free account
  3. 3Write ordered steps
    Add one instruction and one expected result per step, such as signing in, opening billing and confirming the invoice preview. Use environment placeholders for credentials.
  4. 4Run and read the evidence
    Execute a single step, a range or the full project, then review the trace, screenshots and report to see exactly where a failure occurred.
  5. 5Follow the tutorial guide
    Build a login-to-checkout test without test code and deliberately break it to see how failures are reported.
    CueTest — Follow the tutorial guide
  6. 6Connect to CI
    On the Launch plan, trigger runs from GitHub Actions, GitLab CI or any pipeline that can call an API, and gate releases on the returned outcome.
    CueTest — Connect to CI

Pros and cons

Pros

  • Tests are written as plain-language steps, so no selectors need maintainingAI
  • Separate verifier checks each expected result against the live page, not just the agent's claimAI
  • Replays a saved deterministic plan first and uses AI only when the path changesAI
  • Every run returns a trace, screenshots, report and the exact failed stepAI
  • No-signup hosted trial and a free plan with no card requiredAI

Cons

  • Free plan is small: 30 browser minutes, 25 AI resolutions and one active run at a timeAI
  • CI access is listed only on the paid Launch plan, not the free tierAI
  • Usage is metered in browser minutes and AI resolutions, which makes costs harder to predictAI
  • Positioned alongside coded suites rather than replacing them, so teams may run two systemsAI
  • Runs on hosted browsers only, with no self-hosted option mentionedAI

How much does CueTest cost?

Free trial

A hosted trial run needs no signup: one run per browser window, three minutes maximum. The Free plan gives 30 browser minutes monthly, with no card required.

Learn more

Pricing

Free plan at $0 with 30 browser minutes, 25 AI resolutions and a 30-minute maximum run. Launch costs $39 per month with 500 browser minutes, 400 AI resolutions, 3 projects, 2 simultaneous runs and CI access. Extra packs are $10 one-time; extra capacity is $10 per month.

Learn more

Support

The homepage does not describe support channels. A resources section offers research-backed guides on agentic testing, CI/CD use and tutorials.

Learn more

Integrations

Runs can be triggered from GitHub Actions, GitLab CI, or any pipeline able to call an API. It is also pitched as an addition to existing Playwright and Cypress suites.

Learn more

Features

Plain-language ordered steps, reusable step groups, ranged runs, real hosted browsers, independent result verification, deterministic replay with AI healing, trace, screenshot and report evidence, and CI triggering through GitHub Actions, GitLab CI or any API call.

Learn more

Frequently asked questions about CueTest

  • How much does CueTest cost?
    Free plan at $0 with 30 browser minutes, 25 AI resolutions and a 30-minute maximum run. Launch costs $39 per month with 500 browser minutes, 400 AI resolutions, 3 projects, 2 simultaneous runs and CI access. Extra packs are $10 one-time; extra capacity is $10 per month.
  • Does CueTest offer a free trial?
    A hosted trial run needs no signup: one run per browser window, three minutes maximum. The Free plan gives 30 browser minutes monthly, with no card required.
  • Does CueTest have an API?
    Yes, CueTest offers an API.
  • How do you use CueTest?
    The walkthrough on this page covers 6 steps: 1. Try the hosted demo 2. Create a free account 3. Write ordered steps 4. Run and read the evidence 5. Follow the tutorial guide 6. Connect to CI.
  • What platforms does CueTest support?
    CueTest is available on Web App.
  • What does CueTest integrate with?
    Runs can be triggered from GitHub Actions, GitLab CI, or any pipeline able to call an API. It is also pitched as an addition to existing Playwright and Cypress suites.

Status

StatusActive
Views0
Outbound clicks0
Added10/8/2026

Platforms

Web App

Pricing

FreemiumSubscription