New Agentic quality engineering, human-approved

Human judgment.
Agent speed.

A crew of specialised AI agents analyses, designs, automates and validates your tests on every layer. A senior QA lead reviews and approves each step before anything moves forward.

10+ years in test automation ISTQB Advanced Test Analyst Builds enterprise agentic AI Human approval at every step
centaurqa / flow / STORY-218 · Partial refunds for split orders
Example run
CentaurQA delivery flow A story moves through four agent stages: Analyse, Design, Automate and Validate. After each stage a human gate approves the work and passes it on, or rejects it and sends it back to the agent with feedback. Approved automation is merged to development; after the final Go decision the release ships. AI AGENTS HUMAN Story submitsubmitopen PRreport accept approve approve + CI green merge → development Go questions→ PO changesrequested changesrequested No-Gofix & re-run 01 · ANALYSE Requirements Agent 5 sub-agents → analysis report 02 · DESIGN Test Design Agent 6 sub-agents → test cases (Xray) 03 · AUTOMATE Automation Agent 7 sub-agents · runs tests → pull request 04 · VALIDATE Validation Agent 6 sub-agents · regression → release report H1 Accept story PO / QA lead H2 Review test design QA lead H3 Code review QA lead + CI H4 Go / No-Go QA lead + release owner Released ✓

Swipe to follow the flow →

AI agent stage Human approval gate Hand-off for review Approved, moves forward Rejected, back with feedback
The problem

Testing usually starts too late and in the wrong place.

01

Defects born in the requirements

Vague acceptance criteria and contradictory specs become bugs weeks later, when they are the most expensive to fix.

02

Slow, brittle test suites

Most checks run through the UI. Pipelines take hours, flaky tests get ignored, and nobody trusts a red build.

03

Regression without a target

Either everything runs on every release or nothing does. Nobody can say which tests prove that this release works.

Inside each stage

One lead agent per stage. Specialists underneath. A human at every exit.

Each lead agent coordinates its own sub-agents and hands over one structured artefact. The next stage starts only when a human has approved that artefact.

01 · ANALYSE

Requirements Agent

Finds the defects already sitting in the documentation, before anyone writes a test.

  • AC quality analyser
  • Doc consistency checker
  • Traceability mapper
  • Risk classifier
  • Clarification writer

Output: analysis report, risk score, verdict

H1 · Story accepted for testing
02 · DESIGN

Test Design Agent

Turns each acceptance criterion into documented tests on the right layer and reuses what you already have.

  • Layer allocator
  • Functional designer
  • Negative & edge cases
  • Non-functional designer
  • Test data designer
  • Duplicate checker

Output: test cases in Xray, coverage matrix

H2 · Test design approved
03 · AUTOMATE

Automation Agent

Automates the approved tests in your stack and runs them until they are stable. When the product is wrong, it reports a bug instead of bending the test.

  • Framework explorer
  • Reuse planner
  • Layer implementers
  • Runner & stabiliser
  • Failure classifier
  • Self-reviewer
  • PR creator

Output: pull request with passing tests

H3 · Code review, merge to dev
04 · VALIDATE

Validation Agent

Works out what the release changed, selects the regression tests that matter, runs them and explains every failure.

  • Release scope analyser
  • Risk-based selector
  • Environment health check
  • Execution orchestrator
  • Failure triager
  • Reporter

Output: release report, Go/No-Go recommendation

H4 · Go / No-Go decision
Coverage

Every test layer, in the right proportion.

A test pyramid is a ratio, not a drawing. We cover every layer and keep most of the checks where feedback is fastest and cheapest.

LayerWhat the crew checksOwnerTooling we adapt toShare of checks
L0Requirements
Testable acceptance criteria, contradictions between specs, missing cases, traceability
Requirements Agent
Jira, Confluence, OpenAPI, AsyncAPI
Every story
L1Unit
Coverage that means something, mutation testing, test smells, gaps compared with the AC
Unit Reviewer
JUnit, pytest, PIT, mutmut
Most · seconds
L2Contract & integration
Consumer contracts, schema diffs, Kafka event flows, MongoDB and SQL integrity
Automation Agent
Pact, Kafka, MongoDB, SQL
Many · seconds
L3API & system
Business outcomes rather than status codes, isolated test data, REST and GraphQL
Automation Agent
REST Assured, requests, GraphQL
Some · minutes
L4UI
Critical user journeys only, where UI tests pay for themselves
Automation Agent
Playwright, Selenium, Robot Framework
Few · minutes
L5End-to-end
Risk-based regression selected for each release, run in CI, with every failure explained
Validation Agent
GitHub Actions, GitLab CI, Jenkins, Xray, Allure
Fewest · per release
NFRNon-functional
Security, performance and resilience, run alongside every layer instead of at the end
Design + Automation
OWASP ZAP, Semgrep, Trivy, k6, Gatling
Thresholds set by your real requirements

Cloud & infrastructure covered where tests need it: AWS Lambda, S3, Secrets Manager, Docker.

Why a centaur

Not another AI testing tool.

In centaur chess, a human working with a machine beats both the strongest player and the strongest engine. Quality engineering works the same way.

AI testing toolTraditional QA teamCentaurQA
Senior judgment on every resultNoDepends on the teamYes, four approval gates
CoverageMostly UIDepends on the teamRequirements to E2E, plus NFR
Fits your stack and CIIts own platformYesYes, your frameworks and pipelines
Commercial modelLicence plus your team's timeOngoing headcountFixed-scope engagements
Services

Start small. Scale when it proves itself.

Fixed scope, fixed price and clear deliverables. Every engagement starts with a free 30-minute call.

QA Health Check

Start here

1–2 weeks

Fixed price, scoped together
  • Requirements & documentation audit
  • Unit test review with mutation testing
  • Map of your current test layers
  • CI pipeline review
  • Top 10 quality risks, ranked
  • Prioritised roadmap
Book a Health Check

Automation Bootstrap

4–8 weeks

Fixed price, scoped together
  • Test framework in your stack
  • Contract, API, UI & E2E suites
  • Integration with your CI
  • Jira/Xray traceability
  • Performance & security baselines
  • Handover and training
Discuss your project

Continuous QA

Monthly

Fixed price, scoped together
  • The full four-stage flow on every story
  • Review of every test pull request
  • Triage and repair of failing tests
  • Release impact & regression selection
  • Release report with Go/No-Go
Talk to us
Beyond traditional QA

We also test AI, and build agents that are tested.

Chatbots and agents fail differently from ordinary software: the same question can get a different answer. They need their own kind of testing, with the same human sign-off.

AI & chatbot testing

  • Answer quality and accuracy against your own knowledge
  • Hallucinations and answers without a source
  • Prompt injection and data leakage
  • Harmful or off-brand responses and guardrail checks
  • Tool and agent actions: the right call, with the right permissions
  • Regression evaluations in CI for every prompt or model change
  • Latency and cost per conversation

Agentic workflows

  • Internal processes run by agents with human approval steps
  • Ticket triage, document processing and report preparation
  • Integrations with Jira, email, CRM and databases
  • AI and MCP gateways: access, permissions, cost limits and logs
  • Evaluation and guardrails before anything reaches production
The experience behind the crew

Senior quality engineering, built into every agent.

More than ten years of test automation and enterprise software, now combined with hands-on experience building agentic AI systems.

10+years in QA & automation
10engineers led in one team
5industries
ISTQBAdvanced Test Analyst

What the human lead does

  • Sets the test strategy and the risk priorities
  • Designs automation architectures from scratch
  • Reviews and signs off the work at every gate
  • Builds CI/CD quality pipelines
  • Designs agent orchestration, evaluation and guardrails
  • Mentors your team and hands the process over

What the agent crew does

  • Analyses requirements and finds documentation defects
  • Designs tests on the right layer
  • Automates them in your stack and opens pull requests
  • Runs, stabilises and classifies failures
  • Selects risk-based regression for each release
  • Reports results to Jira/Xray with full traceability

Industries

HealthcareAutomotiveCybersecurityEducationOnline gaming

Stack

PythonJavaPlaywrightSeleniumRobot FrameworkREST AssuredrequestsREST · GraphQLKafkaMongoDBSQLAWS Lambda · S3 · SecretsDockerJenkinsGitHub ActionsGitLab CIJira · XrayMulti-agent systems · MCP
Security & trust

How we work with your code.

Your infrastructure first

Our default is to run the agents in your CI or on your machines, with your own AI provider account. We agree the setup with you before any work starts.

Least privilege by default

We ask for read-only access where possible. Merges, protected branches and bug reports stay behind human approval.

Traceable decisions

Each gate is designed to leave a record of who approved what, when, and based on which report.

FAQ

Questions teams ask first.

Something else on your mind? Ask on a call.

Will this replace our QA engineers?

No. It takes the repetitive work off them: document analysis, drafting tests, automating them and triaging failures. That leaves your people free for judgment and exploratory testing. You can also use CentaurQA to set up the process and then run it yourselves.

What if the agents get something wrong?

That is what the four gates are for. Nothing reaches your backlog, your repository or your release decision without a senior engineer reviewing it. The agents also check their own work against strict quality rules before a human sees it.

Do you need access to our source code?

For automation work, yes. Our default is to run the agents in your environment, with read-only access wherever possible and no direct commits to protected branches. A Health Check can start from documentation, specs and CI output alone.

Which tech stacks do you support?

Java, Python and TypeScript test stacks; REST, GraphQL, Kafka and database integrations; GitHub Actions, GitLab CI and Jenkins; Jira/Xray for test management. The agents adapt to your existing frameworks and conventions.

How do we start?

Book a free 30-minute call. We agree on the scope of a Health Check, and within 1–2 weeks you have a clear picture of your quality risks and a roadmap, whether or not you continue with us.

Find out where your quality risks are.

A free 30-minute call, with no sales pitch. You leave with at least one concrete improvement to your testing.