Test Run execution frequency limit per hour for qTest Essentials tier

Question

Selecting a license tier that minimizes cost for a low‑traffic test automation workload requires understanding how the Test Run feature’s execution frequency limit applies across tiers. The documentation notes a maximum number of test cases that can be executed per hour but does not specify whether this limit varies by license level.
For a workload that runs only a few automated tests each day, it is unclear whether the Essentials tier imposes the same hourly cap as higher tiers, what the exact cap is, and what happens when the cap is exceeded—such as throttling, error responses, or additional charges.
What is the documented maximum number of test cases that can be executed per hour in the Essentials tier? Does this limit differ for the Professional, Enterprise, and Enterprise Plus tiers? What behavior occurs when the limit is exceeded (e.g., throttling, error response, or extra fees)?

Muntasir · Answer

Execution Limits in qTest Essentials
There is no publicly documented, universal "test case per hour" cap that applies specifically to the qTest Essentials tier. In the qTest ecosystem, execution frequency is typically governed by API rate limits and the capacity of the linked execution engine (such as qTest Launch), rather than a flat hourly quota tied to the management license tier.

Likely Behavior and Constraints
While a specific hourly number for the Essentials tier is not standardized in general documentation, the following behaviors typically apply across the platform:

API Rate Limiting: qTest manages high-frequency automation via API thresholds. If your automation framework pushes results too rapidly, the system will likely return an HTTP 429 (Too Many Requests) response.
Tier Differentiation: The primary difference between Essentials and Professional/Enterprise tiers usually involves feature access (e.g., advanced reporting, integration depths, and seat counts) rather than a reduction in the hourly execution ceiling.
Execution Engine Bottlenecks: If you are using qTest Launch, the actual limit is often determined by the number of available execution agents or the specific license for the execution engine, regardless of whether the management tier is Essentials or Enterprise.

Verification Steps
Because these limits can vary based on specific contract agreements or instance configurations, use these steps to verify your current environment:

Check Administration Panel: Navigate to the instance administration settings to review any listed API rate limits or usage quotas.
Monitor HTTP Responses: Review your automation logs for 429 error codes during peak execution windows.
Consult the SLA: Review your specific Service Level Agreement (SLA) via the Tricentis Support Portal, as custom limits are often applied at the account level.

Missing Diagnostic Detail
To provide a more precise limit, please specify if you are using qTest Launch or a third-party CI/CD tool to trigger these executions, as the bottleneck often resides in the execution layer rather than the Essentials management tier.

Test Run execution frequency limit per hour for qTest Essentials tier

1 answer

Execution Limits in qTest Essentials

Likely Behavior and Constraints

Verification Steps

Missing Diagnostic Detail

Your perspective belongs here.

0 question comments