Running Tests
Manual test execution in TMS ONE is organised around Test Suites — a named collection of test cases you want to run together. This guide covers creating a test suite, executing tests, recording results, and viewing the final run report.Overview
The manual execution workflow has three stages:- Create a Test Suite — select which test cases to run
- Execute — go through each test case, record outcomes and evidence
- Review Results — view the completed run report with pass/fail summary
Stage 1: Create a Test Suite
1. Navigate to Execute
From the left sidebar, click Execute under your project.2. Create a new test suite
Click the + Create Test Suite button in the left panel.A descriptive name for this test suite.
Example: “Sprint 12 Regression” or “Login Feature Tests”
Example: “Sprint 12 Regression” or “Login Feature Tests”
Select one or more modules. This filters the available test cases to choose from.
Select the test cases to include in this run. You can search by title and use Select All to quickly include all visible test cases.Only Published test cases are available for selection.
Optional. Link Jira tickets to this test suite if your Jira integration is configured.
3. Save the test suite
Click Save. Your test suite will appear in the left sidebar, ready to execute.Stage 2: Execute Tests
1. Start the run
Click on your test suite in the left sidebar to preview it. You’ll see a table listing all the included test cases. Click Execute to begin.2. Work through each test case
The execution screen shows one test case at a time with:- The test case identifier (e.g. TC-001)
- The test steps to follow
- The expected outcome
- A progress bar showing how many cases you’ve completed
Follow the steps listed and compare what happens against the expected outcome. b. Record the outcome Select one of the following results from the Outcome dropdown:
| Outcome | When to use |
|---|---|
| Pass | The test behaved exactly as expected |
| Fail | The test did not produce the expected result |
| Skipped | The test was intentionally not executed |
| Blocked | The test could not be run due to an external dependency |
Use the comment field to describe what you observed, especially for failures. d. Attach evidence (optional)
Upload screenshots or screen recordings (JPG, PNG, MP4, WebM — max 2 files, 100MB each). e. Log a defect if the test fails
When you select Fail as the outcome, a Create Defect button appears. Click it to log a defect directly from the failed test case. f. Move to the next test case
Click Save & Next to save your result and move on.
3. Complete the run
When you reach the last test case, the button changes to Complete Execution. Click it to finalise the run and generate the results report.Stage 3: Review Test Results
After completing a run, you’ll be taken to the Test Runs page where you can view all completed runs. Each run shows:| Column | Description |
|---|---|
| Run ID | Unique identifier (e.g. TR-001) |
| Run Title | Name of the test suite |
| Date Completed | When the run was finished |
| Total | Total number of test cases |
| Passed | Number of passed tests |
| Failed | Number of failed tests |
| Skipped | Number of skipped tests |
| Blocked | Number of blocked tests |
| Not Run | Tests included but not executed |
Editing a test suite
To add or remove test cases from an existing test suite:- In the left sidebar, click the ⋮ menu next to the test suite
- Select Edit
- Update the title, modules, or test cases
- Click Save
Re-running tests
TMS ONE doesn’t have a “re-run failed tests only” option. To re-run a suite:- Click the test suite in the sidebar
- Click Execute again
- All test cases will run from the beginning
Permissions
| Action | Permission required |
|---|---|
| Create test suite | Create Runner |
| Edit test suite | Update Runner |
| Execute tests | Execute Runner |
| Record results | Update Test Case Result |
| Complete execution | Create Runner Result |
| Create defect from failure | Create Defect |
| View test run results | View Runner Result |
| Delete test run | Delete Runner Result |
Looking to automate your tests?
Once you have manual tests running, you can use the Test Builder to generate Playwright automation scripts from your test cases — no coding required.Test Builder
Generate automation scripts from your manual test cases using AI
What’s next?
Execution History
View and review all completed test run history
Defect Management
Track defects logged from failed tests
Inviting Users
Add testers to your project