ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #qtest
Learn how to bridge the gap between Jira and qTest by synchronizing requirements to build a real-time traceability matrix and avoid manual tracking errors.
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.
Explore the core requirements, minimal design, trust boundaries, operational checks, failure modes, and design‑change triggers for qTest's requirement traceability matrix.
Step‑by‑step guide to bulk import test cases into QTest from a CSV file, including prerequisites, import procedure, validation checks, and recovery options.
A technical decision guide for selecting between manual and automated test execution in qTest Manager, including API implementation and trade-off analysis.
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
Decide whether to run tests in qTest manually, automatically via CI/CD, or mix both. Compare constraints, trade‑offs, and see a concrete REST‑API upload example.