# Product facts: methods, controls and limits

> Verified facts about Cue April for buyers and AI assistants: testing methods, integrations, approval controls, evidence, limits and evaluation access.

Source: https://cueapril.com/product-facts
Updated: 2026-10-15
Index: https://cueapril.com/llms.txt

- **What it is:** Cue 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.
- **Testing methods:** Computer-use exploration, unit, API, Playwright, Gherkin, property-based and mutation testing. Execution is subject to the supported stack and qualified runner setup.
- **Repository connections:** GitHub and Azure DevOps connectors are implemented. Repository permissions, source revision, supported suites and live execution readiness are checked during setup.
- **Agent interfaces:** REST API, MCP tools and a CLI are implemented for authorised integrations. Scopes and approval rules continue to apply when an agent calls the product.
- **Human control:** Teams approve the plan, targets, environment actions and run allowance. Human reviewers retain the release decision.
- **Evidence:** Reports retain source identity, expected behaviour, actual outcomes, available artifacts and visible incomplete work. Supported findings can be reproduced and regression drafts reviewed.
- **Access and pricing:** Account creation and organisation setup are self-serve. Connect a repository and review its proposed setup. Execution requires supported tools, a qualified runner and approved scope; paid evaluation terms are agreed before paid testing. 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).
- **Published proof:** The original owned local sample contains 19 task executions: 9 passed and 10 failed, with six mutation survivors. A separately recorded product-engine run on 15 October 2026 publishes nine core unit, API and finite generated-input tasks plus six real fast-check tasks. Both use deliberately seeded faults and contain no customer, model or cloud execution. The product run records a random search that missed a boundary defect alongside the exact check that caught it.
- **Current qualification:** Implemented capability is distinct from a qualified live service. The provider, image, region, methods, data terms and approved environment must be confirmed for each evaluation.
- **Scope limits:** API schema campaigns are not a complete security assessment, and performance workloads have separate requirements. Passing checks do not certify a release, and a mutation score describes only the scope that ran.

## Questions

### What is Cue April?

Cue 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.

### Can Cue April keep testing overnight?

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.

### What is an AI testing agent?

An AI testing agent helps plan and investigate software checks using your requirements and tools. Cue April coordinates an approved plan across multiple testing methods and keeps the results, evidence and unfinished checks available for human review.

### How does it work with our existing tests?

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.

### Can it test AI-generated code?

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.

### Can AI agents do QA testing?

Yes, within limits. An AI testing agent can plan checks, run them repeatedly and report what it found, which frees QA engineers for the judgement calls. Cue April keeps people in charge: your team approves the plan and decides what ships.

### Will AI replace QA testers?

Cue April is built to support QA testers. It takes on repeatable checking and evidence gathering, while testers set the expected behaviour, review the findings and make the release decision with the rest of the team.

### Does an agent decide when we release?

Your team makes the release decision. Passing, failing and incomplete checks remain distinct, and reports retain the findings and evidence gaps that matter to that decision.

### How can we evaluate it?

Create an account to choose an organisation, connect a repository and review a proposed setup. Your team approves the testing scope before a run. Request a walkthrough when you want help with repository support, runner qualification, data handling or commercial terms.

### What does it cost?

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.
