Achieving Live Requirement‑to‑Test Traceability in qTest

When requirements shift during a sprint, test cases often fall out of sync, leaving teams unsure whether coverage still matches the latest spec.

The takeaway: by configuring qTest’s built‑in requirement traceability and optionally automating links with its REST API, you can maintain a live matrix that updates automatically when requirements or tests are added, changed, or removed.

How qTest Stores Requirement Links

In qTest, each requirement and test case is a distinct object. A traceability link is a bidirectional association stored on the requirement record; the platform does not duplicate test case data, it merely records the identifier of the linked test case. This design lets you see, from a requirement, which test cases verify it, and from a test case, which requirements it satisfies.

Linking via the UI

1. Open the requirement you want to trace.
2. Click the Traceability tab.
3. Press Link Test Case, search for the test case, and confirm.
4. Repeat for additional test cases or use the Bulk Link option to select many at once.

The UI instantly shows the linked test cases under the requirement and adds a reverse link on each test case’s traceability tab.

Automating Links with the API

For teams that generate requirements or test cases programmatically, the qTest REST API can create the same links without manual clicks. The following example assumes you have a personal API token with the Test Management scope and know the project, requirement, and test case identifiers.

# Replace placeholders with your actual values
curl -X POST "https://.qtestnet.com/api/v3/projects//requirements//test-cases//link" \
  -H "Authorization: Bearer " \
  -H "Content-Type: application/json" \
  -d '{}'

Where:

• is your qTest SaaS subdomain (e.g., company).
• , , and are numeric IDs obtainable from the URL when viewing the object.
• The request body can be empty; the endpoint creates the link if it does not already exist.
• A successful call returns HTTP 200 with a JSON payload confirming the link.

To remove a link, use the analogous DELETE endpoint /requirements//test-cases//unlink.

Validating the Traceability Setup

After linking—whether via UI or API—you can confirm the association by retrieving the requirement object:

curl -X GET "https://.qtestnet.com/api/v3/projects//requirements/" \
  -H "Authorization: Bearer "

Inspect the linkedTestCases array in the response; it should contain the TC_ID you just linked. Similarly, fetching the test case will show a linkedRequirements array with the REQ_ID. If the arrays are empty, the link was not created—check token scopes, IDs, and any API‑rate‑limit responses (HTTP 429).

Limitations and Practical Checks

• Subscription tier: Advanced traceability features such as bulk linking and API access are available only on Professional or Enterprise plans; Basic plans restrict you to manual UI linking.
• API rate limits: SaaS enforces a limit of 150 requests per minute per token; bulk operations should be paginated or throttled.
• Manual cleanup: Deleting a requirement or test case does not automatically remove its links; orphaned references remain in the audit log and must be cleaned via API if needed.

A practical way to verify ongoing traceability is to schedule a lightweight job that, once per day, GETs a sample of requirements and asserts that the count of linkedTestCases matches the expected number from your source of truth (e.g., a requirements management tool). Any mismatch triggers an alert for investigation.

Next Steps

1. Audit your current qTest project to see which requirements already have traceability links.

2. If you are on a qualifying tier, generate an API token and test the link‑creation call in a sandbox project.

3. Incorporate the link‑creation step into your CI/CD pipeline whenever a new requirement is authored or a test case is added.

4. Set up the daily verification job described above to catch drift early.

By combining qTest’s native traceability with disciplined API automation, you turn a manual, error‑prone process into a reliable, continuously updated artifact that supports both compliance and agile velocity.