Repository and test case management
Organize test cases in folders and track structure, status, and latest execution results.
Modern test management for QA and engineering teams.
TestOrchestrator helps teams organize test cases, execute runs, manage workflows, and control access across projects in one secure workspace.
Multi-tenant workspaces
Runs, workflows, and account email verification
Role-based access control
Runs and results
Explore the product
Explore key areas of the platform, including reporting, repository management, and test execution.
Overview and delivery visibility
View milestones, execution activity, and project timelines at a glance.
Everything your team needs
The platform already supports core test management workflows used by real teams.
Repository and case management
Organize test cases into folders, track activity, attach supporting files, and keep structured case metadata inside tenant-scoped projects.
Runs and result execution
Create test runs, assign cases, capture results, attach evidence, navigate execution state, and review progress at run level.
Sessions and execution templates
Support session-oriented testing with session templates, configurable fields, and workflow-aware status transitions.
Workflows, statuses, and configurations
Configure workflow states, statuses, milestones, and platform configurations so teams can shape execution to match their release process.
RBAC and user administration
Four-tier access control covers workspace access levels, global roles, project membership, and optional project-level role overrides.
External reference workflows
Link cases, runs, and sessions to external issues and integration sources so testing activity stays connected to delivery work outside the platform.
What teams use it for
TestOrchestrator is aimed at teams that need operational control, not lightweight note- taking.
QA leadership
Standardize repository structure, workflow states, team permissions, and project access without leaking data across tenants or workspaces.
Engineering delivery
Coordinate release testing, track milestone readiness, and move quickly between test assets, run execution, and external issue references.
Operations and workspace admins
Manage onboarding, invitations, authentication settings, password policy, and role assignment from a dedicated administrative surface.
Growing multi-project organizations
Keep a single product model while isolating tenants, separating permissions, and shaping project-level access without duplicating environments.
Transactional email use cases
Email is used for user-account and workspace actions only. Recipients are either users who initiate signup themselves or users explicitly invited by a workspace administrator.
1. Signup verification
New workspace creators receive an email verification link before account activation is completed.
2. Workspace invitations
Tenant administrators invite named users into a workspace with explicit access level and role context.
3. Welcome and onboarding notices
Accepted invitees can receive onboarding email that points them back to the correct tenant workspace login entry point.
4. Email change verification and alerts
Email changes trigger verification to the new address and a security alert to the old address so the account owner can detect unauthorized changes.
5. Optional invitation cancellation notices
Invitation lifecycle email can notify users if an invitation is cancelled before it is accepted.
6. Email delivery and monitoring
The intended production posture is verified domain sending, DKIM signing, and bounce and complaint monitoring through Amazon SES event handling.
How the product is structured
TestOrchestrator separates the public entry point from tenant workspaces so teams land in the right environment.
- Root domain hosts the public product, contact, privacy, terms, and security pages.
- Tenant subdomains host authenticated workspaces and route users to the right environment.
- Tenant API subdomains handle authenticated product traffic independently of the public site.
- This keeps public content and authenticated workspace activity clearly separated.
Why this matters
Teams get a clear public entry point while project access, roles, and execution work remain scoped to the correct workspace.
Security and tenant controls
The product is shaped around tenant isolation, access control, and operational account protection. See the dedicated page for more detail.
Tenant isolation
Data access is scoped by tenant context and reinforced through backend tenant-aware filtering and row-level protection patterns.
Least privilege RBAC
Access is separated by workspace access level, global role, project membership, and optional project overrides.
Authentication controls
Password policy, lockout behavior, verification flows, and external identity support are part of the administrative model.
Start using TestOrchestrator
Request early access to see how your team can manage test execution, workflows, and access control in one place.