ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to push CI automated test results to qTest Manager via its REST API, using a stable mapping strategy, worked example, and notes on limits and common pitfalls.
Deciding which tool owns which data — Jira for work items, qTest for test design and execution — turns traceability from a pre-release scramble into a byproduct of daily QA work.
qTest's Requirement Traceability Matrix links requirements, test cases, and defects into a live coverage view. Here's how to set it up, verify it, and avoid its main pitfall.
Step‑by‑step guide to bulk import test cases into QTest from a CSV file, including prerequisites, import procedure, validation checks, and recovery options.
Learn how to separate Planned and Execution Test Cycles in qTest Manager to keep reporting clean and quality gates accurate.
Pushing CI test results into qTest via its REST API unifies manual and automated coverage — but the real work is stable ID mapping and idempotent submission, not the API call itself.
Goal I want to exercise our CI pipeline's integration with the qTest Manager REST API — creating test runs and submitting automated test results — without using production credentials or writing results into our live project. The plan is a separate sandbox or trial project with its own API token, generated by a least-privilege account, so a leaked token in C
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
Migrating a small qtest test suite between projects while preserving execution history and requirement traceability. The UI bulk copy generates new test case IDs, breaking links to historical runs and requirement associations, and may time out on larger suites. The REST API allows custom field mapping and scripted moves, but test runs are read‑only and canno
qtest