Number of Seats/Users: Tricentis qTest offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Tricentis qTest that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Tricentis qTest. Tricentis qTest reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Tricentis qTest offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Tricentis qTest. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Tricentis qTest often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Tricentis qTest is generally seen as a strong, Jira‑centric test management platform, with a few consistent friction points that matter for both productivity and cost.

What Spendbase clients like most
– Strong Jira integration
– Easy linking of requirements, test cases, and defects to Jira stories and bugs.
– Bi‑directional visibility: execution status in Jira, bugs created in Jira directly from qTest.

• Solid fit for Agile teams
• Supports releases, sprints, story boards, color‑coded status, milestones.

• Works well for daily use in Scrum and broader SDLC tracking.

• Test case and execution management

• Simple creation, organization, and execution of test cases.

• Helpful version control, attachments, copy/paste, batch approvals, parameters, and environment reuse.

• Basic reporting and traceability

• Infographics and summary reports give a clear picture of test progress.
• Good traceability from requirements to test runs and releases.

Key pain points our clients flag
– Performance and stability
– Slow queries and refresh, especially in the Insights module or when many projects are selected.
– Occasional UI glitches, timeouts, and minor bugs while saving or viewing steps.

• Reporting and Insights
• Insights is often called slow and not very intuitive compared to standard analytics tools.

• Out‑of‑the‑box reports miss some expected “basic” views and visual coverage dashboards.

• Jira and requirements syncing

• Requirement counts between Jira and qTest sometimes do not match.
• Manual tagging of many items to a single story is time‑consuming.

• Requirement management and traceability setup can feel clunky.

• Usability gaps

• Some workflows feel counterintuitive (e.g., where to add tests to suites).

• UI looks dated to some teams, and non‑QA users struggle to get comfortable.

• Automation and ecosystem

• Limited support for certain third‑party automation tools; a push toward Tosca.

• Not many built‑in features for automation workflows in some setups.

• Pricing sensitivity

• Several Spendbase clients call out qTest as slightly or highly overpriced versus alternatives.

Spendbase discount insight
– Because many teams mainly use qTest for Jira integration and manual test management, our internal benchmarks suggest you can often reduce cost by:
– Limiting full licenses to active QA users.
– Questioning add‑on modules like Insights if adoption is low.
– Using usage data to negotiate better pricing tiers or module bundles with Tricentis.