Bulk Import Test Cases into QTest Using CSV
Step‑by‑step guide to bulk import test cases into QTest from a CSV file, including prerequisites, import procedure, validation checks, and recovery options.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
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
Goal is to keep operational alerts useful without notification noise in QTest. QTest offers per-user notification subscriptions for project events such as test runs, requirements changes and defects. Controls are managed through user profile and project subscription settings with opt-in per object type and role. Delivery is limited to objects the user can ac
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