Skip to main content

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:
  1. Create a Test Suite — select which test cases to run
  2. Execute — go through each test case, record outcomes and evidence
  3. 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.
Title
text
required
A descriptive name for this test suite.
Example: “Sprint 12 Regression” or “Login Feature Tests”
Module(s)
multiselect
required
Select one or more modules. This filters the available test cases to choose from.
Test Cases
multiselect
required
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.
Jira Tickets
multiselect
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
For each test case: a. Perform the test steps
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:
OutcomeWhen to use
PassThe test behaved exactly as expected
FailThe test did not produce the expected result
SkippedThe test was intentionally not executed
BlockedThe test could not be run due to an external dependency
c. Add a comment (optional)
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.
The page automatically scrolls to the top when a new test case loads. Your progress is saved as you go — you won’t lose results if you need to pause.

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:
ColumnDescription
Run IDUnique identifier (e.g. TR-001)
Run TitleName of the test suite
Date CompletedWhen the run was finished
TotalTotal number of test cases
PassedNumber of passed tests
FailedNumber of failed tests
SkippedNumber of skipped tests
BlockedNumber of blocked tests
Not RunTests included but not executed
Click the view icon on any run to see the full breakdown.

Editing a test suite

To add or remove test cases from an existing test suite:
  1. In the left sidebar, click the ⋮ menu next to the test suite
  2. Select Edit
  3. Update the title, modules, or test cases
  4. Click Save

Re-running tests

TMS ONE doesn’t have a “re-run failed tests only” option. To re-run a suite:
  1. Click the test suite in the sidebar
  2. Click Execute again
  3. All test cases will run from the beginning
Previous execution history (comments, attachments, results) is preserved for reference.
There is no partial re-run feature. The entire suite must be executed again. You can however create a new test suite with only the failed test cases if needed.

Permissions

ActionPermission required
Create test suiteCreate Runner
Edit test suiteUpdate Runner
Execute testsExecute Runner
Record resultsUpdate Test Case Result
Complete executionCreate Runner Result
Create defect from failureCreate Defect
View test run resultsView Runner Result
Delete test runDelete 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