qatouch-dark-logo

Request a Demo

Get started - it's free 

Requirements Mapping

QA Touch requirements and traceability

Trace Every Requirement to Its Test Cases.

Link requirements to test cases, then check coverage in a matrix QA Touch generates for you. Export it as XLSX or share a read-only link for reviews and audits.

  • Two-Way Requirement and Test Case Links
  • Automatic Requirement Traceability Matrix
  • Bulk Mapping by CSV, XLS or XLSX
  • Read-Only Coverage Links Without a Login
Get Started
See How It Works

Tester

Quality starts here
  • Create and manage test cases.
  • Execute test runs.
  • Report and track defects.
Sprint 14 runillustrative

Developer

Fix faster, ship sooner
  • Receive and resolve defects.
  • Collaborate with QA.
  • Track issues and development progress.
Defect lifecycleillustrativeOpenIn reviewFixed
QA TouchShared workspace

Manager

Confident release decisions
  • Monitor team productivity.
  • Track release readiness.
  • View reports and quality metrics.
Release 2.4 readinessillustrative

AI Test Case Generation

Less repetitive manual work
PromptJira storyBRDFigmaAPI spec
12test cases drafted
Repetitive manual effortillustrative

You review and edit before saving.

Requirements traceability in QA Touch

Know Which Requirements Have Tests, and Which Do Not

QA teams need proof that what was asked for is being tested. In QA Touch, requirements and test cases live in the same project and link in both directions. The matrix then shows the coverage of each requirement.

  • Makes coverage gaps visible for each requirement
  • Replaces one-by-one mapping when a project has many requirements
  • Gives reviewers a coverage view without a QA Touch login
Illustrative traceability map Requirement R0001 links to test cases TC-1 and TC-2, and requirement R0002 also links to TC-2, so both requirements are Covered. Requirement R0003 has no linked test case, so it is Not Covered. RequirementsTest casesRTM coverage R0001R0002R0003TC-1TC-2 CoveredCoveredNot Covered

Illustrative example. A requirement with no linked test case shows as Not Covered.

Key capabilities

Requirements Management With Traceability Built In

Trace coverage across your test cases, and keep the planning material behind it in the same project.

Map and trace

Connect requirements to test cases and report on the result.

Capture and plan

Organize requirements, ideas and project documents.

How it works

Capture, Link, Then Verify Coverage

Select a task to see its documented steps and what you get at the end.

Requirements and traceability workflows
Capture
Link
Verify

Create a mind map

Outline use cases quickly before writing a full set of test cases.

  1. Open your project and click Mindmap in the left navigation menu.
  2. Click Create a Mind map and enter a mind map name.
  3. Click the Default Text node, then the + icon to add nodes.
  4. Rename the Default Text and the other nodes, then click Save.
Result: A saved mind map in your project.Read the guide (opens in a new tab)

Map requirements in bulk

First import the requirements and test cases into the project.

  1. On the Test case List page, open the import menu, click Requirement (bulk mapping) and download the sample file.
  2. Enter requirement codes separated by commas, such as R0001,R0002,R0003.
  3. Map your file's fields to QA Touch test case fields. API Key and Requirement are mandatory.
  4. Click Update.
Result: Requirements mapped to test cases. Only active requirements are updated.Read the guide (opens in a new tab)

View the Requirement Traceability Matrix

No matrix to build by hand: QA Touch generates it automatically.

  1. Go to Requirements → Requirement Traceability (RTM) → Traceability Matrix.
  2. Review each requirement's ID, name and linked test cases.
  3. Check the coverage status of Covered or Not Covered.
Result: A matrix you can export as XLSX or share through a read-only link.Read the guide (opens in a new tab)

Benefits for QA teams

Fewer Blind Spots. Easier Reviews.

What changes when requirements and test cases are linked in one project.

  • Coverage gaps you can see

    Not Covered sits next to the requirement it applies to, so missing test cases show up without cross-checking separate lists.

  • Less one-by-one mapping

    A single bulk import can link many requirements to similar or different test cases, instead of mapping each one individually.

  • Evidence ready for reviewers

    An XLSX export gives you a file for client reviews, audits and compliance documentation.

  • Visibility without extra logins

    A read-only link lets stakeholders check coverage and execution status without signing in to QA Touch.

  • Use cases mapped out first

    A mind map lets you pen down use cases in less time before committing to a full set of test cases.

  • Project context in one place

    Attachments keep project files where the team can review requirements, deliverables and activities.

Real-world use cases

Where Traceability Helps Each Role

Everyday situations, and how each person handles them in QA Touch.

  • Tester

    Plans before writing cases

    I want to outline this workflow before writing the test cases.

    Create a mind map in the project, add a node for each use case and rename them as the workflow takes shape. Share it with team members to improve communication.

  • QA engineer

    Maps a large requirement set

    I have to link hundreds of test cases to their requirements.

    Enable the mapping queue, then fill in the sample file with comma-separated requirement codes. Imports of more than 300 test cases run in the background while you carry on working.

  • QA manager

    Prepares for a client review or audit

    Which requirements still have no test case?

    Open the Traceability Matrix and look for Not Covered. Once the gaps are closed, export the RTM as XLSX for the review or your compliance documentation.

  • Project manager

    Keeps stakeholders informed

    Can the client see coverage without a QA Touch login?

    Yes. Share the RTM's public read-only link so stakeholders can view requirement coverage and execution status without logging in.

Setup and configuration

Prepare Your Project for Traceability

These are the preparation steps the guides call out before you start mapping.

Get requirements and test cases in place

The bulk mapping guide lists these prerequisites.

  1. Import the requirements into the project.
  2. Import the test cases into the project.

Requirement codes, such as R0001, are found on the requirement itself.

Mapping file rules

  • CSV, XLS or XLSX sample file
  • Columns: API Key, Test Case name and Requirements code
  • The API Key is system-defined and cannot be changed
  • Only active requirements are updated

Read the bulk mapping guide (opens in a new tab)

Turn on the mapping queue

Use this for mapping imports of more than 300 test cases.

  1. Go to Administration, then Site Settings.
  2. Enable Queue Enable/Disable For Importing requirement mapping with Test Cases.

What changes

  • Imports run in the background
  • Regular work is not affected
  • The guide says queued imports use less time and bandwidth

Read the queue section (opens in a new tab)

Add project files

Keep documents such as a business description document or project plan with the project.

  1. Log in to QA Touch.
  2. In the left panel, click Attachments.

Limits in the guide

  • Each file must be under 2 MB
  • A project can have a maximum of 10 attached files
  • Allowed file types are shown in the guide

Read the attachments guide (opens in a new tab)

QA Touch requirements and traceability

Frequently Asked Questions

What is the Requirement Traceability Matrix in QA Touch?

The RTM (opens in a new tab) tracks the relationships between requirements, test cases and test execution. QA Touch generates it automatically under Requirements, with each requirement’s ID, name, linked test cases and coverage status.

Yes. One requirement can map to multiple test cases, and one test case can map to multiple requirements.

Open the Traceability Matrix and check the coverage status column. Each requirement shows as Covered or Not Covered.

On the Test case List page, use the import menu’s Requirement (bulk mapping) option. Enter comma-separated requirement codes in the sample file (opens in a new tab), map the fields, and click Update. Archived and deleted requirements are not updated.

Yes. A public read-only link lets stakeholders view requirement coverage and execution status without logging in. You can also export the RTM as XLSX.

On the Requirement page, click the Linked test case count. From the other side, click a test case title on the Test case page and open the Linked Requirements tab.

The Attachments guide (opens in a new tab) says each file must be under 2 MB, and a project can have a maximum of 10 attached files.

Connect Your Requirements to Your Test Cases

Link your first requirement in QA Touch, then see its coverage in the Traceability Matrix.

Get Started
Read the RTM Documentation