ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #qtest
Learn how to link requirements to test cases in qTest using the UI and REST API, verify the links, and understand tier‑based limitations and verification practices.
Learn how to create, manage, and automate Test Runs in QTest. Follow this step‑by‑step guide to set up runs, assign owners, execute cases, generate reports, and use the REST API for CI/CD integration.
qTest's filterable test run history lets you slice execution data by status, assignee, and custom fields — then bulk-update and export exactly that slice. Here's how to use it without tripping over permissions or stale exports.
QTest's traceability matrix creates live links between requirements and test cases, showing coverage gaps and enabling bulk actions. Learn how to set it up, generate reports, and avoid performance issues.
A decision guide for integrating automated test results with Tricentis qTest: compare the REST API, Automation Host agents, and Jira-linked workflows, with a concrete validation plan.
Learn how to post a JSON array to QTest’s bulk import endpoint, handle partial successes, and work around size and validation limits.
Duplicate test cases in Qtest and Jira waste time. This guide shows how to set up a robust Qtest‑Jira integration, map fields, and verify syncs—so you keep a single source of truth for test cases and defects.
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.