Treat test cases like product code: draft, review, publish
Versioned test management keeps an editable draft, immutable published versions, optional peer review, library stages, and fork/rollback — so AI-speed authoring stays governed.
Mohsin Muhammad
Senior QA Engineer
AI can draft a journey in minutes. The question that decides whether that speed helps or hurts is simple: who owns the published truth, and can you roll it back?
Orcastrator’s test management answers that the way good product teams already answer for application code — with versions, review, and immutability.
A case is a container, not a file
Each test case holds:
- At most one editable draft
- Many published versions that never change once shipped
- Stages and steps (with commands and configuration) that orchestrations actually run
Orchestrations execute published versions. Drafts are for work in progress — blank, copied from a prior publish, or an in-place edit of the latest published version that only persists when you save, publish, or request publish.
Publish with the control you need
The Publish action adapts to permissions and project settings:
- Request Publish sends the draft for peer review (approve, reject with comments, or cancel)
- Direct publish ships immediately when both the author permission and the project “allow direct publishing” setting are on — without weakening immutability
Trusted authors can still opt into review from the same split-button. Saving a draft that is already in review auto-cancels the request so reviewers never see stale content.
Suites, tags, and the Library
Cases live in suites, carry tags for selection and filtering, and can pull shared library stages — login, data setup, common verification — defined once and reused across cases. Update the library stage; consumers stay consistent without copy-paste drift.
Fork and roll back without archaeology
Need a variant of a published path? Fork from any version into a new case. Need yesterday’s behaviour back? Roll back to a prior published version as the base for a new draft. History stays inspectable; production runs stay pinned to known publishes.
Why this matters next to Sonar
Sonar and MCP can mint ghost steps and live-author flows quickly. Test management is the gate: nothing becomes the version orchestrations run until a human saves and publishes. That is the difference between “AI wrote a test” and “the team owns a test.”
Governance is not ceremony. It is how velocity stays trustworthy.
Keep reading
More from the blog.
Quality in the age of AI
When software can be built faster than teams can confidently trust it, the answer may not be more testing. It may be a shared product language for quality.
Hamza Abdullah
CEO
Your product needs a coverage map, not another pass-rate chart
Blueprints turn modules, journeys, and services into a living area map — with criticality, specs, tests, gaps, and impact links that Pulse and orchestration can actually use.
Lyba Fatima
Senior QA Analyst
Self-healing is not enough — you still need a coverage map
Healing locators cuts maintenance. It does not tell you which critical journeys are untested when AI ships ten PRs before lunch.
Taimour Shoaib
QA Engineer