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.
Developer
Fix faster, ship sooner- Receive and resolve defects.
- Collaborate with QA.
- Track issues and development progress.
Manager
Confident release decisions- Monitor team productivity.
- Track release readiness.
- View reports and quality metrics.
AI Test Case Generation
Less repetitive manual workYou 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.
Run it against a release
Execute the work and follow its status.
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.
- Illustrative scenarioGiven a registered user
BDD test cases
Write test cases in the Given-When-Then format so technical and non-technical team members can read the same scenario. Import BDD test cases from an XML file with BDD Script Import.
Explore BDD test cases
When they submit a valid password
Then they reach the dashboard (opens in a new tab) Test plans
Set the baseline before testing begins. Choose Default for predefined components, or Blank to add your own.
Read the guide (opens in a new tab)Releases
Split a project into phases, which Agile teams call sprints. Each release shows as Open, Upcoming or Completed.
Read the guide (opens in a new tab)Sample templates
Start a project from templates for domains such as Ecommerce, Mobile Applications, Finance and AI-based testing.
Read the guide (opens in a new tab)Reusable test steps
Keep shared steps in a suite and use them across test cases. Auto Sync reflects updates between reusable steps and test case steps.
Read the guide (opens in a new tab)Reusable BDD scripts
Build Gherkin-keyword steps once, then reuse them across the scenarios or test cases that match.
Read the guide (opens in a new tab)Test case reviews
Track each case as Pending, Approved, Rejected or Re-Verify, along with its current state and related timelines.
Explore reviews (opens in a new tab)Version history
See what changed in each version, who changed it and when, then compare versions with additions, deletions and modifications highlighted.
Explore version history (opens in a new tab)
Run, organize and migrate
Execute tests, keep large sets in order and bring in existing cases.
- IncludeAll test cases, specific cases or specific modulesAssignChange the assigned user for all cases and stepsImportCSV, XLS or XLSX with column mappingExportIncludes the case count for each statusQueueRuns over 500 test cases in the backgroundCompleteMark this Test Run as Completed (opens in a new tab)
Test runs
Create a run from every test case or a filtered selection, assign it to a user, and tie it to a release. Results can be Untested, Blocked, Failed, In Progress, Not Applicable, Passed or Retest.
Read the test run guide Stepwise execution
Log each step's status, the user who ran it and any attachments. The parent test case status updates from its steps.
Explore stepwise execution (opens in a new tab)Test run bulk update
Update the status of every case in a run, or only those in a selected module, at once.
Read the guide (opens in a new tab)Elapsed time
Record execution time with an Auto Timer or manual entry, in HH:MM:SS, for test cases and their steps.
Read the guide (opens in a new tab)Copy test cases
Copy a test case, a module or all test cases within a project or to another one. You can also restrict duplicates.
Read the guide (opens in a new tab)Import and bulk update
Export existing test cases, edit them in a spreadsheet, and import the changes to update fields in bulk.
Read the guide (opens in a new tab)Tag management
Apply tags to one or many test cases, then bulk add or remove them directly from search results.
Read the guide (opens in a new tab)Normal and advanced search
Find cases by title keywords, or filter by tags, type, priority, template type, created by, test suite, mode and status.
Read the guide (opens in a new tab)Migrate from other tools
Export from TestRail, TestCollab or PractiTest, then import a CSV or single-sheet Excel file with field mapping.
Read the guide (opens in a new tab)Migrate from TestLink
Convert a TestLink XML export to QA Touch XML, then import it as Test Case (Text) or Test Case (Steps).
Read the guide (opens in a new tab)
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.
Create a test plan
A test plan describes the scope, approach, resources and activities for testing.
- In the left panel, click Project List and open your project.
- In the test cases section, click Add Test Plan (+), then Add Test Plan.
- Enter a test plan name.
- Select a Test Plan Type: Default or Blank.
Add and follow a release
Release status follows its dates, or you can mark a release completed before its End Date.
- Go to Project → Releases and click + Add Release.
- Enter the details and click Save.
- Click View Issues to see the code, summary, status and priority of each issue.
- Click Sharable Release View and hover over the pie chart for test run status percentages.
Create a reusable steps suite
Write common steps once for use across the test cases in your project.
- On the Test case list page, go to Add → Reusable Steps and click Add.
- Enter the suite name.
- Enter a Step Description and Expected Result, then click + for more steps.
- Click save.
Create a reusable BDD script
Scripts generally start with Given, except for Feature and Background.
- In your project, click Testcases, then add → Reusable BDD Script, then Add script.
- Enter a name for the script and a required Feature name.
- Click the (+) icon and select keywords from the dropdown.
- Save the script.
Bulk update existing test cases
Use a CSV, XLS or XLSX file. The case API Key cannot be changed and is mandatory in mapping.
- On the Test cases list page, click Import (Bulk Update) and download the existing test cases file.
- Edit the columns for the fields you want to change.
- Upload the file and map the columns.
- Click Import and confirm the updates.
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.
- On the test case page, open the action menu and choose Copy All.
- Select the destination project.
- Optionally select Do you want to restrict Duplicate while Copying Test cases?
- Click Copy.
Add a test run
Pick every test case, or a specific set narrowed down with filters.
- Go to Project → Test Runs and click + Add Test Run.
- Select All Test Cases or Specific Test Cases, and use Filter to narrow a selection.
- Enter the test run name, and select the user and release.
- Click Save.
Filter cases, then create a test run
Useful when a project holds a large number of test cases.
- On the Test case page, select the search option.
- Under Filter Criteria, choose criteria such as test suite, priority, tags or status.
- Create a test run from the filtered results.
Bulk update test run statuses
Choose global to cover the whole run, or module based to cover one module.
- Global: click Bulk update under Actions.
- Module based: select the module and click the bulk update option at module level.
- Select a status and click save.
Record elapsed time on a result
Use Auto Timer controls for Start, Stop and Reset, or enter the time manually.
- On the Test result list page, click the Add result icon.
- Select the status.
- Add elapsed time with Auto Timer or Enter Manually.
- Click Save.
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 stepI 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 issuesWhich 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 regressionI 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 progressWhere 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.
- Create a new project.
- Select a Sample Test Case Template that matches your project requirements.
- The template is added to your project automatically.
- 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.
- Export your test cases from the current tool.
- In QA Touch, go to Project Overview, then Test Cases > Data Migration.
- Choose TestRail in the options and upload the CSV file.
- 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.
Convert, then import
Export your data from TestLink in XML format first.
- In your project's Test Case module, go to Test Cases → Data Migration TestLink XML.
- Upload the TestLink XML file and click Download to get the converted QA Touch XML.
- On the Test Case page, open Import XML and choose a template.
- Upload the QA Touch XML file and click Import.
Import templates
- Test Case (Text)
- Test Case (Steps)
The guide covers test cases. It does not list other data types, such as test runs or attachments.
Enable the queue for large test runs
Queued test runs with more than 500 test cases run in the background.
- Go to Administration → Site Settings.
- Turn on Queue Enable/Disable For Test Run.
Create test case tags
Add tags here, then apply them to your test cases.
- Go to Administration → Custom option.
- Open the Test Cases tab, click Tags and add new tags.
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.
Which result statuses can a test case have in a test run?
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.
Can I reuse test steps and BDD scripts?
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.
Which tools can I migrate test cases from?
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.
Can I update many test cases at once?
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.
Can people outside QA Touch see release progress?
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.
How is execution time recorded?
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.