ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #qtest
Logs from a recent qTest deployment contain the exact error string "Test run failed: Unable to locate test execution context" when the Test Execution Engine cannot match a test run ID. The Test Execution Engine is responsible for scheduling, launching, and tracking test runs during deployment. Current behavior halts the deployment without any automatic retry
Integration Between QTest Deployment History API and Jenkins When a Jenkins‑triggered deployment fails, the QTest Deployment History UI offers a compressed log download link, but the REST API only returns a temporary URL. The URL typically expires within 15 minutes, and the API does not provide the raw log content directly. This gap makes automated log colle
Goal Prevent accidental exposure of test artifacts by revoking or expiring public URLs once the Public Access toggle is disabled. Current State Enabling the Public Access toggle creates a permanent read‑only URL that remains valid until the toggle is turned off. However, disabling the toggle does not invalidate URLs that have already been generated; they con
QTest's documented upgrade recovery path relies on restoring a pre‑upgrade database and file‑system backup rather than an automatic rollback. The upgrade wizard does not revert schema changes or re‑apply custom configurations when it aborts mid‑process, leaving administrators to reconcile any partial updates manually. A gap remains in the official guidance:
Symptom When iterating the qTest public REST API search endpoint (POST /projects/{id}/search with object_type filters) using page and page_size, the combined result set does not match the project contents: some test cases appear on two pages while others never appear at all, even though the total-count metadata stays consistent. Context The goal is a reliabl
jenkins