How it works

From user story to green run: how a QA team creates, automates, and maintains its tests in one place — without losing the manual testing that still matters.

Get started freeRead the docs
Phase 1
Set up
Release & requirements
Phase 2
Author
Manual test cases
Phase 3
Automate
Agents & live runs
Phase 4
Maintain
Triage, assign, report
Phase 1 · Set up

Give the team one place to work

Everything starts with a release and a clear statement of what to test.

1

Your team’s home base

Create a project and release

A project groups related releases; a release holds the test cases, runs, and reports for one application or team. Create both from Settings, then invite teammates by email.

  • Invite QA engineers, developers, and stakeholders as members
  • Owners and admins manage settings; members author and run tests
  • Each release keeps its own test cases, history, and KPIs
2

Start from the user story

Capture requirements as acceptance criteria

Paste a user story — or attach the spec as PDF, DOCX, images, or code — and the AC Generator produces Gherkin-style acceptance criteria you can review, edit, and save to the release.

  • Given/When/Then criteria generated in seconds
  • Attach supporting files for richer context
  • Saved criteria become the source of truth for coverage tracking
Try the AC Generator
Phase 2 · Author

Build the manual test suite

Manual tests are the foundation — generated from acceptance criteria or written by hand, executed with structure, and tracked like everything else.

3

From criteria to executable checklists

Generate manual test cases

Turn each acceptance criterion into a full set of manual test cases — happy path, negative, boundary, edge, validation, security, and accessibility scenarios — or write your own from scratch in any release.

  • Steps or BDD (Cucumber) format — your choice
  • Every generated case is editable before you save it
  • Set priority, type, and component so reports stay meaningful
Try the Test Case Generator
4

Structured manual testing

Execute manual runs and record results

Work through manual test cases step by step and record pass/fail per case. Results land in the same execution history as automated runs, so your reports show one unified picture.

  • Mark cases passed, failed, or blocked as you go
  • Failures carry notes and context for whoever investigates
  • Every result feeds release KPIs automatically
Phase 3 · Automate

Promote the suite to automation

Automate the repetitive cases in plain English and run them on real browsers with agents you control — manual and automated results share one history.

5

Plain-English automation — no code required

Convert manual cases to automated tests

Promote any manual test case to an automated one. Steps stay in plain English — "Fill Username with standard_user", "Click Login", "Verify Products is visible" — and the runner resolves them against the live page.

  • AI converts manual steps into automation-ready steps
  • Smart selectors match labels, placeholders, roles, and test-ids
  • Need real code instead? Generate Playwright, Cypress, or Selenium projects too
Try the Code Generator
6

Real browsers, live feedback

Run tests on your own agents

Install the TestPerfect Agent on any machine — a laptop, Docker container, or VM — and dispatch automated tests to it from the dashboard. Watch steps execute live with screenshots and logs streamed back.

  • Chromium, Firefox, and WebKit supported
  • Step-by-step screenshots and console logs in real time
  • Uses your configured AI provider (Claude, OpenAI, or Gemini) for smart step resolution
Phase 4 · Maintain

Keep the suite healthy

Tests only earn trust if failures get investigated and metrics stay visible. Triage, assignment, and reporting close the loop.

7

Every failure has an owner

Investigate failures and assign follow-ups

Each run gets a detail page with per-step results, screenshots, and errors. Assign failing runs or test cases to teammates with a note — they see everything on their Assignments page.

  • Full run history with step-level evidence
  • AI-assisted step fixing for broken automated steps
  • Assignments track who is investigating what, and why
8

Prove the testing is working

Track quality with release KPIs

Reports show pass rates, automation coverage, flaky tests, execution trends, and per-release KPI breakdowns — filterable by project, release, and time range.

  • Pass rate, coverage, and automation split per release
  • Flaky-test detection from execution history
  • Build custom reports for the metrics your team cares about

Ready to try the full workflow?

The generators are free to use without an account. Sign up to save test cases to a release, run them on agents, and bring your team along.

Create your releaseStart with a user story