FREE ON THE AZURE DEVOPS MARKETPLACEtest management / azure devops

Know what
to automate.
Then let your AI do it.

Test cases, suites, runs and exploratory testing stored in your own Azure DevOps — plus an automation score for every manual test, and a direct line to Copilot, Claude Code or Cursor to write the test. No Test Plans licence.

› Your data stays in your ADO — never on a Testaro server› Your AI, your key or your editor — never ours› No per-user licence — unlike Azure Test Plans
testaro@ado — bash
Total
248
Passed
228
Failed
20
Pass rate
92%
cron pipeline
01Install
02Author
03Run
04Report
// automate when it's worth it

Score. Hand off. Close the loop.

Most teams automate by gut feel. Testaro scores every manual test from the data you already have, hands the right ones to the AI you already pay for, and keeps the score as your pipeline takes over.

01

Score — no AI

Runs often with the same outcome, data-driven or Given/When/Then, guards a smoke or regression suite, clear steps: up. Needs human judgement or flips between runs: down. Every score shows its reasons.

02

Hand off

One click gives a ready prompt for your editor, or the Testaro MCP server lets Copilot, Claude Code or Cursor read the case and write the test in your repo. Prefer the hub? Your own AI key reviews it there.

03

Close the loop

The pipeline task reports results into Testaro; the case flips to automated on its own, and its builds are watched for flaky, failing or stale — with a fix suggestion from your AI.

Automation candidates — manual tests ranked with the reasons for each score
Automation candidates — ranked, with the reasons
Automated tests with their pipeline health: passing, flaky, failing, stale
Automated — watched for flaky, failing and stale
// your AI, three ways

We never hold a key.

Use the AI your company already licenses, bring your own key, or use none at all. The scoring works without any.

AI.01

The AI in your editor

Testaro's MCP server runs on the developer's machine with their own Azure DevOps token. Copilot, Claude Code or Cursor fetch candidates, write tests, mark them automated. Testaro never sees a key or a prompt.

AI.02

Your own key, in the hub

For testers who live in Azure DevOps: paste a key in AI settings and get a verdict, what to tighten, and a test skeleton — session-only, never stored, never logged.

AI.03

No AI at all

The score, the reasons, the editor prompt and the pipeline health need no model and send nothing anywhere. Add AI when you want it.

// everything QA needs

One hub. Whole process.

From writing the first case to shipping with confidence — without paying per tester for Test Plans.

01

Lives in your ADO

Cases, suites, runs, and history stored natively in your own Azure DevOps. No separate database, no third-party telemetry.

02

Knows what to automate

Every manual test gets a score from your own runs, suites and steps — with the reasons — and a health check once a pipeline reports it. No AI needed.

03

Bring your own AI

Generate, refine, and triage tests with your own AI key. Prompts go straight to your provider — never through us.

04

Reports & coverage

Pass rates, requirement traceability, trends, exploratory sessions, plus shareable read-only links.

05

Scheduled runs

Generate a cron pipeline that runs your tests and reports results back into Testaro — governed by admin approval.

06

No Test Plans licence

Everything Azure Test Plans charges per-user for — manual testing, suites, runs, reporting — without the cost.

07

Built for teams

Soft admin governance, custom fields, shared steps, and review workflows so a growing QA team stays organised.

// see it in action

A real hub, inside ADO.

Dark-mode, fast, and filled with your own data — no Test Plans licence, nothing leaving your tenant.

Automation candidates — what to automate, and why
Automation candidates — what to automate, and why
Overview — release readiness at a glance
Overview — release readiness at a glance
Test cases — author, tag, filter, organise
Test cases — author, tag, filter, organise
Runs — execute, compare, re-run failures
Runs — execute, compare, re-run failures
Scheduled runs — cron on your pipelines
Scheduled runs — cron on your pipelines
Security — where your data and keys live
Security — where your data and keys live
// built to be trusted

Security you can rely on

Clear about exactly where your data and keys live.

SEC.01

Your data stays yours

Stored in your own Azure DevOps organisation. We don't hold your test data on any Testaro server.

SEC.02

Keys never leak

AI keys are session-only — never stored, never logged. With a company key, requests run server-side so users never see it.

SEC.03

Least-privilege

Scoped Azure DevOps permissions, admin-gated writes, and clients that never touch the database directly.

// get started

Ship with confidence.

$ install → open hub → your data stays in your ADO
01Install from Marketplace
02Open the Testaro hub
03Data stays in your ADO
Add to Azure DevOps — start free