ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
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
qtest