The refreshed qTest Manager user experience becomes available to all users in August 2026, giving release owners a clear decision point on adoption before teams depend on future interface improvements.
Users may still opt out of the new experience. That choice has a material operating consequence: opted-out users will not receive future improvements as Tricentis continues development on the new user interface.
What changes in August
The August release moves the refreshed qTest Manager experience from a staged introduction to broad availability. This is primarily a workflow and adoption change, not a migration of test data, requirements, test cases, executions, or defects.
For enterprise teams, the important distinction is between access and readiness:
- The new experience is available to every user.
- Users can opt out if a critical workflow needs more validation.
- Opting out limits access to future interface improvements.
- Teams should avoid treating opt-out as a permanent operating model.
The release notes also indicate that feature availability can roll out gradually. Administrators should account for short timing differences between environments when scheduling communications or validation activities.
Why release owners should care
A navigation and interface change can affect release execution even when test assets remain unchanged. Test managers, manual testers, automation leads, business reviewers, and quality approvers often use different paths through qTest. Small changes in navigation, hierarchy views, or rich-text editing can alter the time needed to locate evidence, update execution status, or review a release.
The operational risk is not data loss. It is inconsistent work practices during an active release window.
Release owners should confirm that teams can still complete the workflows that support release decisions:
- Find the correct release, test cycle, suite, and test run.
- Review failed and blocked executions quickly.
- Update execution evidence and linked defects.
- Navigate requirement-to-test traceability.
- Export or retrieve the evidence required for governance reviews.
- Escalate interface issues through a defined support route.
Treat opt-out as a governed exception
The ability to opt out is useful for teams with a documented blocker, such as a critical business workflow that has not completed validation. It should not become an unmanaged user preference.
A practical exception policy includes:
- A named business or technical reason for opting out.
- An owner accountable for remediation.
- A target date for rejoining the new experience.
- A record of affected projects and release windows.
- Periodic review by the qTest platform owner.
This approach gives teams time to manage genuine disruption without creating a permanent split between user populations. Two interface models across a large QA organization makes training, support, and process assurance more difficult.
Governance and audit considerations
The August update does not state that qTest approval controls, traceability records, or audit history have changed. Still, organizations with formal quality systems should assess the interface rollout under their normal change-control process.
Focus validation on the points where people create, review, approve, or retrieve quality evidence. For regulated delivery teams, capture concise proof that representative users can perform required actions and that documented procedures still match the live interface.
Useful evidence may include:
- Screenshots or test records from critical workflows.
- Updated work instructions and training references.
- Results from role-based user acceptance checks.
- Approved exceptions for users who temporarily opt out.
- A communication record that explains the future-improvement limitation.
This is usually a proportionate change assessment, not a full platform revalidation. The correct scope depends on how deeply qTest supports controlled release, CSV, or audit processes in your organization.
Recommended adoption plan
Start with representative users rather than a generic announcement. Include manual testers, test leads, release managers, automation engineers, Jira integration owners, and quality governance stakeholders.
- Identify the workflows that are release-critical.
- Validate those workflows in the refreshed interface.
- Update internal job aids, screenshots, and support guidance.
- Publish the opt-out criteria and expiration process.
- Monitor support demand during the first active release cycle.
- Review exceptions and remove them once blockers are resolved.
Teams that previously piloted the new navigation should still run a brief readiness check. Broad availability changes the support model: help desk, platform administration, and release leadership now need a shared answer for users who encounter differences in their daily work.
How Merito helps
Merito helps enterprise teams turn qTest release changes into controlled operating practices. We assess critical test-management workflows, define adoption and exception governance, update runbooks, and help align qTest usage with Jira, CI/CD, compliance, and release-management processes.
For organizations using qTest across multiple business units, Merito can also establish common readiness criteria so local teams do not make inconsistent interface decisions. That reduces avoidable support load and keeps release evidence practices consistent.
Merito is an authorized Tricentis reseller and services partner, listed as a Certified Solution Partner in the Tricentis partner directory. Our Tricentis qTest team can scope licensing, sizing, and rollout for August 2026, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.