What Testuvion does
From documentation to approved test cases, and proof for both
Testuvion reads the specifications you already have, maps the processes in them, generates test cases grounded in those documents, and keeps the trail from every case back to its source.
Four modules. You run the ones you need.
Documentation analysis · test cases · automation · run and evaluation. Switch off what you don’t need, and take the output of any stage away with you.
Index
An indexed corpus, and a proposed process hierarchy.
Upload specifications, business concepts, decks, spreadsheets, diagrams and screenshots.
Map
A process tree that test cases attach to, with coverage measured per process.
Rearrange the proposed hierarchy to match how the project actually runs.
Generate and approve
Test cases that cite the document and section behind them
Choose the level of detail, then filter, edit inline and approve — individually or in bulk, with a record of who approved what.
Automate
A runnable Playwright project, downloaded as a ZIP
Approve the cases you want automated. You get tests/, pages/, helpers/, playwright.config.ts and package.json — extract it, npm install, run.
Where the test cases come from
A person directs the run. The documents decide what it can say.
You set the scope and the level of detail
Grounded in your indexed documents, never the model’s prior knowledge
Every case cites the document and the section it came from
Only what a step needs is passed to the model — never the whole corpus
No support in the documentation, no case
Coverage field · cropped to one case
Who can do what, and what gets recorded
Role-based access
Scoped per project, and per role inside it.
SSO / OIDC
Your own identity provider. Microsoft Entra ID is supported today.
Approval on every case
Who approved which case, and when. Capture is automatic.
Append-only activity log
Actions taken by agents are recorded separately from actions taken by people.
Spend ceilings
Set per team and per person. A run stops at its ceiling rather than asking afterwards.
Private deployment
Run it in your own environment, against a model you provide.
Planned, not available today
Direction, not commitments. Nothing here has a date, and nothing here is part of what you buy today.
- 01API testingNew surface
- 02Bulk import of test cases you already haveImport
- 03Scheduled and CI-triggered runsAutomation
- 04Regeneration when your documentation changesMaintenance
- 05Cypress and Postman as automation targetsFrameworks
- See the full roadmap →
Where Testuvion hands over
Four boundaries, stated plainly. Each one is a point where the product stops and your team or your tooling takes it on — which is also why nothing here locks you in.
Your tools
Open formats out, no lock-in
The source of truth while you generate and approve. After export, cases live wherever the process expects them — Jira, Xray or CSV. Not a test-management tool, and not trying to become one.
Your pipeline
Runnable projects, executed downstream
Testuvion produces the project. Execution belongs to the CI you already have.
Your team
A person decides what ships
The authoring and the maintenance work go away. Judgement does not — every case carries a named decision.
Your call
Regeneration happens on request
When documentation or the application changes, nothing updates quietly. Regenerating is something you trigger.
See it run on your own specification
Bring a functional specification to the call. We’ll run a narrowed part of it live and walk through the output together, and you’ll have the complete generated suite within 24 hours.