ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #qtest
When Jenkins publishes automated test results to qTest Manager via the integration plugin, the system maps JUnit XML outputs to specific test cases based on identifiers. A challenge arises when multiple Jenkins agents or parallel stages execute the same logical test case simultaneously or in rapid succession. The integration boundary defines how qTest handle
qTest Launch associates automated results with qTest Manager test cases, and that association is a configuration choice rather than a single fixed behavior. Two documented approaches are commonly used: embedding the qTest test case ID in the automated test name or metadata and extracting it in the parser, or matching the exact automated test name to the qTes
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
jenkins