Keep the journeys that matter in view.
Run supported browser suites and investigate approved user journeys. Review what actually happened, with retained evidence for the next decision.
Browser and journey testingAI testing for engineering and QA teams
Cue April is an AI testing agent for engineering and QA teams. Reuse supported tests from GitHub or Azure DevOps, approve a plan and review the findings with evidence.
Check 10,001 sample basket amounts in your browser. No account or payment required.
Test a sample invoice app. See the failing case and the evidence behind it.
Fictional data, deliberate bugs. Generate 10,001 basket amounts and check the delivery rule, then run eight regression cases. Everything runs in your browser. No repository, AI calls or hosted runner is used.
Runs only the supplied invoice example in your browser, using fictional data and no AI calls. It does not test your repository or consume paid testing allowance.
Focus the investigation on the behaviour your team expects.
Your approved change scope
Plans · coordinates · reports
Approved scope & allowanceTested revision · expected behaviour · evidence
Explore the handoff. Actual checks depend on your approved plan, available runners and spending limit.
Build on the tools your team already uses.
Inspect an actual product-engine run
See Cue April’s unit, API and generated-input engines execute an owned invoice example. Compare corrected code with two deliberate faults and inspect the retained results.
Recorded locally. No customer data, hosted runner or AI calls.
Take testing off your to-do list
Every new feature creates more work to test. Cue April gives that work a quality lead: someone to coordinate the investigation, repeat the checks and bring the findings back to you.
See the handoffBring your requirements and a code change. Your quality lead proposes the methods and targets, using the tests you already have where supported.
Run the approved checks, explore tricky inputs and challenge weak assertions. Keep the work moving on a schedule or when watched code changes.
Review findings tied to the tested revision, with the evidence to investigate them. Reproduce supported failures and review regression drafts for the next run.
ILLUSTRATIVE TEAM STRUCTURE
More testing capacity. Less coordination.
Start with one change. Bring more methods into the plan as the release gets bigger. Your quality lead coordinates specialist checks across the scope you approve, bringing the results together for review.
Independent tasks can run in parallel where supported. Scheduled and watched-change runs keep approved checks moving without someone manually starting every investigation.
Go deeper than a green tick
A release can look fine in the browser and still get a business rule wrong. Combine different ways to investigate the same change.
Run supported browser suites and investigate approved user journeys. Review what actually happened, with retained evidence for the next decision.
Browser and journey testingCheck API behaviour and challenge business rules with generated inputs. Test against expected behaviour your team has reviewed, including when a coding agent wrote the implementation.
Property-based and API testingIntroduce controlled changes to a copy of the code and see whether your tests notice. Keep surviving mutations visible, so weak assertions become work you can act on.
Test the tests with mutation testingMake room for what comes next
Coding agents can produce more changes than your team has time to inspect. Give testing its own quality lead, working from requirements your team approves.
Explore the workflowHand off repeat runs and evidence gathering. Keep your testers focused on requirements, unfamiliar risks and the judgement calls that need a person.
Explore the workflowSee what passed, what failed and what still needs attention against the actual change. Bring that context into your pull request review.
Explore the workflowLet your software prove the value
Choose how much of the work you want to hand over.
Put agents to work
Create an account, connect a repository and review your first plan. Start with the change that matters to you, then build a standing testing workflow around your team.
Create accountScope and pricing are confirmed before paid testing.
Have us run it for you
Our managed service handles setup, checking and reporting. A person reproduces every failure. You approve the requirements and decide what ships.
Two-week pilot · £1,490 or $1,950excluding VAT (20% for UK customers)
Compare pricing and ways to startCue April is an AI software testing agent for engineering and QA teams. It proposes a test plan for a code change, runs the checks your team approves across seven testing methods, from unit and API tests to property-based and mutation testing, and returns each finding with the evidence behind it.
Yes. Set a schedule or watch selected branches to start approved checks automatically. Your configured runner, approved scope and spending limit govern each run. If setup, approval or allowance blocks testing, that stays visible for your team to resolve. Execution availability and support terms are confirmed during evaluation.
Repository inspection discovers supported existing suites and proposes a setup for review. Your team chooses the revision, requirements, methods and execution scope before approving a run. GitHub and Azure DevOps connectors are implemented; supported stacks and live runner availability are confirmed during evaluation.
Yes. The testing workflow can investigate changes regardless of who wrote them. Its expectations should come from independently reviewed requirements, so generated code and generated tests do not simply repeat the same mistaken assumption.
Managed QA testing, where we run the checks for you, starts with a two-week pilot at £1,490 or $1,950, then £1,900 or $2,500 a month, excluding VAT (20% for UK customers). Pricing for running Cue April yourself is agreed for the scope of an evaluation, and the walkthrough request carries no purchase commitment. Scope, run allowances and commercial terms are confirmed before paid work begins.
Your next release starts here
Give Cue April your next testing challenge. Let your AI quality lead coordinate the checks, so your team can focus on what comes next.
Run a local sample without an account. Create an account when you’re ready to review your own repository setup.
Prefer to talk it through?
Pick a time for a 30-minute discovery call. We’ll discuss your software, the work you want to hand over and the best way to get started.
Calendar provided by Cal.com. Calendar not loading? Open it on Cal.com. No time that suits? Email us.