Tight Tosca integration
Native integration means Tosca test runs and results flow into qTest without custom glue.
Tricentis • Test management
qTest is Tricentis's test management backbone. Merito configures it so traceability, execution, and reporting run as one motion instead of three.
qTest rollouts set up project structure, requirement-to-defect traceability, Jira or Azure DevOps sync and reporting dashboards, and bring test history across from Quality Center, Zephyr, Xray or TestRail so nothing starts over.
What it is
Tricentis qTest is the test management platform in the Tricentis portfolio. It handles test-case management, execution orchestration, traceability from requirements to defects, and enterprise-grade reporting across automated and manual tests.
qTest is the product that lets a QA program answer "what tests did we run, which ones passed, and which requirements are still uncovered?" without assembling data across four tools. On Tosca footprints, qTest is the traceability layer. On mixed automation footprints with Tosca, Selenium, Playwright, and manual tests, qTest is the unifying management surface.
Configuration, Jira and Azure DevOps integration, traceability design, and training for test managers and engineers make up the core rollout. Just as important, Merito migrates customer test data into qTest from legacy tools like HP ALM, Micro Focus Quality Center, Zephyr, Xray, and TestRail, so test cases, execution history, defect links, and traceability do not get left behind when customers move platforms.
That migration work is how customers retain the investment they have made in their existing test footprint. A qTest purchase should not mean starting over. Merito's approach preserves test assets, history, and audit trails so the value compounds inside qTest from day one.
Ideal use cases
What it is best at
Native integration means Tosca test runs and results flow into qTest without custom glue.
qTest is not Tosca-only. Selenium, Playwright, Cypress, and manual test runs can all report into qTest for unified reporting.
Requirement-to-test-to-defect traceability with full audit trail is what regulated QA organizations need, and what qTest was designed for.
Core capabilities
Test case authoring, organization, and lifecycle across releases and cycles.
Test case management
Structured test case authoring with folders, tags, and version history.
Test cycle and release management
Organize test execution by release, cycle, and environment.
Manual and automated test execution
Run and track both manual and automated test results in one system.
The primary reason enterprise QA teams buy qTest.
Requirement-to-test traceability
Link requirements to test cases to defects with full audit trail.
Coverage dashboards
Real-time coverage views for release readiness conversations.
Executive reporting
Scheduled reports for QA leadership and release stakeholders.
Where it fits in the stack
Deployment and implementation
Licensing and packaging
qTest Manager
Core test management, traceability, and execution.
Best for: Any enterprise QA program.
qTest Insights
Extended analytics and cross-project reporting.
Best for: Organizations running test programs across multiple products.
Merito services
Pick the engagement that matches where you are in the lifecycle.
Setup, project structure, traceability, and reporting configuration.
Explore serviceMigrate test cases, execution history, defects, and traceability links from legacy tools like Quality Center, Zephyr, Xray, or others into qTest. Customers retain the investment made in their existing test footprint.
Explore solutionqTest paired with Tosca or open-source automation for unified management.
Explore serviceqTest licensing
Tell us your QA team size, automation mix, and which legacy tool your test history lives in. Setup, traceability design, and CI/CD integration are scoped from there.
Merito point of view
Merito's experience is that customers often over-buy qTest seats and under-configure traceability. The result is a license bill bigger than the value delivered. The fix is not fewer seats. It is better traceability design in the first month so the seats actually justify themselves.
qTest is most valuable for QA organizations with mixed automation footprints (Tosca plus Selenium plus manual, for example) where unified management matters. For Tosca-only shops at small scale, qTest may be overkill, and Merito will say so.
A qTest purchase should not mean abandoning years of test assets. Merito migrates test cases, execution history, defect links, and requirement traceability from legacy tools (Version One, Quality Center, Zephyr, TestComplete, Excel) into qTest so customers retain the QA investment they have already made. This is the step most reseller-only engagements skip, and it is the step that decides whether qTest launches with credibility or starts from zero.
qTest is not an SAP Solex product and does not have an SAP-branded edition. It is a standalone Tricentis purchase regardless of whether SAP ECT is also in scope.
What buyers usually underestimate
Proof
Healthcare provider
75% fewer manual test cases, and release test cycles cut from 4 to 6 weeks to under 10 days across Epic and 250+ integrated applications.
Workday automation
300+ Workday business processes automated, with test execution cut from 15 minutes to 2 minutes per test, an 85% productivity improvement.
Cencora
More than 250,000 test records across 115 projects moved from Zephyr Enterprise to qTest within two months, 750+ users onboarded and testing cycles 15% shorter.
As of October 6, 2026, the newest Tricentis qTest release Merito has covered is October 2026. Read the October 2026 summary
Active development
Fresh analysis of recent Tricentis qTest releases, reviewed by Merito as they ship.
View all product release updatesTricentis qTest October 2026 lets Tosca Cloud users convert existing cases into linked qTest cases and send cases in either direction. Teams can unlink cases to edit them or disable the integration for a project, while Canadian users gain the ca-central-1 region.
Tricentis qTest September 2026 rolls out the refreshed qTest Manager user interface to all users. The update standardizes visual presentation across the product while allowing a temporary opt-out; however, opting out excludes users from future enhancements built on the new interface. Release owners should plan communications, role-based validation, and a controlled adoption path before making the new experience their organizational standard.
Tricentis qTest August 2026 rolls out the refreshed qTest Manager user experience to all users, following a phased introduction. Organizations can still opt out of the new interface, but opting out prevents access to future user-interface improvements. The practical priority is controlled adoption: update operating guidance, validate critical workflows, and monitor user readiness across QA and release teams.
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Share your QA team size, automation mix, and traceability requirements. A Merito qTest specialist follows up within one business day.
Right-sized licensing
Seat counts follow your actual QA team size and test volume, not bundled defaults.
Traceability-first setup
We configure qTest for real requirement-to-test-to-defect traceability so release decisions have evidence.
Test data migration
Merito migrates test cases, execution history, defects, and traceability from HP ALM, Quality Center, Zephyr, Xray, and TestRail so customers retain their QA investment.
Next step
A Merito qTest engagement kicks off with project structure, traceability design, and integration with your requirement source.
Proof and resources
Most test management migrations fail for data model, relationships, and scale issues. Learn how Merito protects historical QA data and delivers trusted migrations for qTest, Xray, Zephyr, Octane and Jira.
OpenText AQM vs Tricentis qTest is a decision on QA governance and delivery model. This guide helps enterprises choose based on risk, traceability, and scalable SDLC outcomes.