QA Touch test management

Manage Every Test From Plan to Release.

Plan releases, write reusable test cases and execute runs step by step in one workspace, with review statuses and version history on the cases your team relies on.

  • Test Plans, Releases and Test Runs
  • Reusable Steps and BDD Scripts
  • Review Statuses and Version History
  • Test Case Migration From TestRail and TestLink

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.

Test management in QA Touch

Your Test Library and Your Test Execution, Connected

QA teams need a place to prepare tests and a way to follow them through a release. In QA Touch, test cases live in modules within a project. Test runs pick up those cases and tie the results to a user and a release.

  • Avoids rewriting the same steps across test cases
  • Makes large test case sets easier to find, filter and update
  • Shows the status of test runs under each release

Build your test library

Prepare the test cases your team will run.

Test planScope, approach, resources and activities
Test casesSteps or BDD, organized in modules
ReviewPending, Approved, Rejected or Re-Verify

Run it against a release

Execute the work and follow its status.

Test runSelected cases, an assigned user and a release
ResultsStatus for each case and step
Release viewTest run status percentages and related issues

Key capabilities

Test Case Management and Test Execution in One Place

The features your team uses before a run, during it and when moving test cases around.

Plan and write

Structure the project, then write and control your test cases.

Run, organize and migrate

Execute tests, keep large sets in order and bring in existing cases.

How it works

From Test Plan to Test Run, Step by Step

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

Test management workflows
Plan
Build and organize
Run and measure

Create a test plan

A test plan describes the scope, approach, resources and activities for testing.

  1. In the left panel, click Project List and open your project.
  2. In the test cases section, click Add Test Plan (+), then Add Test Plan.
  3. Enter a test plan name.
  4. Select a Test Plan Type: Default or Blank.
Result: A test plan with predefined components, or components you add yourself.Read the guide (opens in a new tab)

Add and follow a release

Release status follows its dates, or you can mark a release completed before its End Date.

  1. Go to Project → Releases and click + Add Release.
  2. Enter the details and click Save.
  3. Click View Issues to see the code, summary, status and priority of each issue.
  4. Click Sharable Release View and hover over the pie chart for test run status percentages.
Result: Release status, an issue list and a test run pie chart.Read the guide (opens in a new tab)

Create a reusable steps suite

Write common steps once for use across the test cases in your project.

  1. On the Test case list page, go to Add → Reusable Steps and click Add.
  2. Enter the suite name.
  3. Enter a Step Description and Expected Result, then click + for more steps.
  4. Click save.
Result: A suite you can reuse, and export as XLS, XLSX or CSV.Read the guide (opens in a new tab)

Create a reusable BDD script

Scripts generally start with Given, except for Feature and Background.

  1. In your project, click Testcases, then add → Reusable BDD Script, then Add script.
  2. Enter a name for the script and a required Feature name.
  3. Click the (+) icon and select keywords from the dropdown.
  4. Save the script.
Result: A saved BDD script for matching scenarios or test cases.Read the guide (opens in a new tab)

Bulk update existing test cases

Use a CSV, XLS or XLSX file. The case API Key cannot be changed and is mandatory in mapping.

  1. On the Test cases list page, click Import (Bulk Update) and download the existing test cases file.
  2. Edit the columns for the fields you want to change.
  3. Upload the file and map the columns.
  4. Click Import and confirm the updates.
Result: Updated active test cases. Archived or deleted cases are not updated.Read the guide (opens in a new tab)

Copy all test cases to a project

Other options copy single test cases or modules to an existing module, a new module or another project.

  1. On the test case page, open the action menu and choose Copy All.
  2. Select the destination project.
  3. Optionally select Do you want to restrict Duplicate while Copying Test cases?
  4. Click Copy.
Result: Copied test cases. Copies of more than 300 run in a background queue.Read the guide (opens in a new tab)

Add a test run

Pick every test case, or a specific set narrowed down with filters.

  1. Go to Project → Test Runs and click + Add Test Run.
  2. Select All Test Cases or Specific Test Cases, and use Filter to narrow a selection.
  3. Enter the test run name, and select the user and release.
  4. Click Save.
Result: A test run assigned to a user and a release.Read the guide (opens in a new tab)

Bulk update test run statuses

Choose global to cover the whole run, or module based to cover one module.

  1. Global: click Bulk update under Actions.
  2. Module based: select the module and click the bulk update option at module level.
  3. Select a status and click save.
Result: The same status on every case in the run or the selected module.Read the guide (opens in a new tab)

Record elapsed time on a result

Use Auto Timer controls for Start, Stop and Reset, or enter the time manually.

  1. On the Test result list page, click the Add result icon.
  2. Select the status.
  3. Add elapsed time with Auto Timer or Enter Manually.
  4. Click Save.
Result: Cumulative time for the test case, module and test run. Step times are counted separately.Read the guide (opens in a new tab)

Benefits for QA teams

Less Repeated Work. A Clearer Record.

What day-to-day testing gains when plans, cases and runs share one workspace.

  • Less rewriting of common steps

    A reusable suite holds steps once, and Auto Sync reflects updates between reusable steps and test case steps.

  • A standard format from day one

    Sample templates add test cases and fields to a new project, giving beginners and the wider team a standard structure to extend.

  • Clear accountability during execution

    Runs have an assigned user, and stepwise logs show each step's status, who ran it and any attachments.

  • A record of how each case evolved

    Each test case has a unique version identifier, and field changes create a new version with the user and time recorded.

  • Large jobs that stay out of your way

    Queueing is available for test runs over 500 test cases, and copies of more than 300 run in the background so regular work is not interrupted.

  • Progress your stakeholders can open

    Shareable release report links can be viewed without logging in to QA Touch.

Real-world use cases

The Questions Each Role Can Answer

Everyday situations, and where each person finds the answer in QA Touch.

  • Tester

    Executes a run step by step

    I need to log every step of this case and the time it took.

    Log a status for each step as you go, and add attachments. The parent case status updates from its steps, and elapsed time totals appear in the Status History.

  • Developer

    Follows up on issues

    Which issues came out of this release's test runs?

    Click View Issues on the Release page to see each issue's code, summary, status and priority. BDD scenarios give you the same Given-When-Then view as the rest of the team.

  • QA manager

    Prepares a sprint regression

    I need a run of the high-priority regression cases.

    Filter by test suite and priority, then create a test run from the results. Check Approved, Rejected or Re-verify status with the same filters before you assign the work.

  • Project manager

    Tracks release progress

    Where does this release stand right now?

    Open the Sharable Release View and hover over the pie chart to see the percentage of each test run status. Share the report link with people who do not log in to QA Touch.

Setup and configuration

Start Fresh or Bring Your Test Cases

Choose where you are starting from. Each route links to its QA Touch documentation.

Start from a sample template

Pick a ready-made test case structure while you set up a project.

  1. Create a new project.
  2. Select a Sample Test Case Template that matches your project requirements.
  3. The template is added to your project automatically.
  4. Modify or extend the sample test cases as needed.

Domains in the guide

  • Ecommerce
  • Mobile Applications
  • Finance
  • AI-based testing

Templates guide (opens in a new tab) · Test plan guide (opens in a new tab)

Bring test cases from another tool

The guide covers exports from TestRail, TestCollab and PractiTest.

  1. Export your test cases from the current tool.
  2. In QA Touch, go to Project Overview, then Test Cases > Data Migration.
  3. Choose TestRail in the options and upload the CSV file.
  4. Map the file's fields to QA Touch fields and click Import.

File rules

  • CSV, or Excel with a single sheet
  • Headers in the first row
  • Module name and Test case title are mandatory
  • Each step and expected result on a separate row

In TestRail, enable Include separated steps on separate rows when you export.

Read the migration guide (opens in a new tab)

Enable the queue for large test runs

Queued test runs with more than 500 test cases run in the background.

  1. Go to Administration → Site Settings.
  2. Turn on Queue Enable/Disable For Test Run.

Read the test run guide (opens in a new tab)

Create test case tags

Add tags here, then apply them to your test cases.

  1. Go to Administration → Custom option.
  2. Open the Test Cases tab, click Tags and add new tags.

Read the tag guide (opens in a new tab)

QA Touch test management

Frequently Asked Questions

How do test plans, releases and test runs differ?

A test plan describes the scope, approach, resources and activities for testing. A release is a project phase with its own deliverables, which Agile teams call a sprint. A test run is the set of test cases you execute, assigned to a user and a release.

The test run guide lists Untested, Blocked, Failed, In Progress, Not Applicable, Passed and Retest. When you import a test run without mapping a status, the default is Untested.

Yes. Reusable steps (opens in a new tab) work across the test cases in a project. Reusable BDD scripts (opens in a new tab) apply to scenarios or test cases that match their steps.

The migration guide (opens in a new tab) covers CSV exports from TestRail, TestCollab and PractiTest. A separate guide (opens in a new tab) covers TestLink XML. The TestRail guide lists mapped columns, test steps and custom fields, and the TestLink guide covers test cases only.

Yes. Import (Bulk Update) (opens in a new tab) changes fields such as title, type, priorities, tags and custom fields in active test cases. Archived and deleted test cases are not updated.

Yes. Shareable report links from the Release page can be viewed without logging in to QA Touch and can be shared publicly, so check what you share first.

Elapsed Time (opens in a new tab) uses an Auto Timer or manual entry in HH:MM:SS. Case times add up to the module and test run totals. Step times are counted separately and are not added to those totals.

Bring Your Test Management Into QA Touch

Start a project from a sample template, or migrate the test cases you already have.