Skip to main content

​
Test Builder (Automation Scripts)

The Test Builder allows you to generate executable Playwright automation scripts from your manual test cases using AI. Instead of writing automation code by hand, you describe your test steps and the AI generates a ready-to-run script in your chosen language.

​
How it works

You provide test steps, a target URL, and optional test data scenarios. The AI generates a Playwright automation script that can be executed directly from TMS ONE. Results are tracked in Execution History. 
Manual Test Case (optional link)
        ↓
  Test Builder — fill in steps, URL, language
        ↓
  AI generates Playwright script
        ↓
  Save to Script History
        ↓
  Execute scripts
        ↓
  View results in Execution History

​
Quickest way: Automate directly from a test case

The fastest way to generate an automation script is directly from your test cases list — no need to navigate to the Test Builder manually.
  1. Go to Test Cases in your project
  2. Find the test case you want to automate
  3. Click the magic wand icon (Automate) in the Actions column
  4. You’ll be taken straight to the Test Builder with the test case pre-linked and details pre-populated
  5. Add the Page URL, review the steps, and click Generate Test Script
This is the recommended way to automate existing manual test cases — it saves time and automatically maintains the link between your manual test case and the generated automation script.

​
Creating an automation script from scratch

​
1. Navigate to Test Builder

From the left sidebar, click Test Builder under your project. You can link an existing manual test case to pre-populate the form and maintain traceability between your manual and automated tests.

​
3. Fill in the generation form

​
Test Title
text
required
A name for the automation script.
Example: “Login flow - valid credentials”
​
Page URL
text
required
The full URL of the page being tested.
Example: https://yourapp.com/login
​
Test Steps
table
required
Define the actions the automation should perform. Each step has three parts:
FieldDescriptionExample
ActionWhat to doclick, type, verify, scroll
SelectorThe element to target#email, button[type='submit']
TextData key or valueemail, password
Click + Add Step to add more steps.
​
Scenario Data
table
Optional. Add multiple test data combinations to run the same script with different inputs. Each row is a separate scenario.Example:
Scenario Titleemailpassword
Valid admin loginadmin@company.comAdmin123!
Valid user loginuser@company.comUser123!
You can also import scenarios from a CSV file.
​
Module
select
Optional. Associate the script with a module in your project.
​
Priority
select
Optional. Set a priority for this automation script.
​
Jira Tickets
multiselect
Optional. Link Jira tickets if your Jira integration is configured.

​
4. Generate the script

Click Generate Test Script. The AI will produce a Playwright script based on your inputs, shown in the right panel.
The more precise your selectors and actions, the better the generated script. Use specific IDs or data attributes where possible.

​
5. Review and edit

You can edit the generated script directly in the code editor before saving. This is useful for adjusting selectors, adding assertions, or tweaking logic.

​
6. Save the script

Click Save Test Script. The script is saved to your project’s script history and is ready to execute.

​
Managing saved scripts

Navigate to Test Builder → History to see all saved automation scripts for your project. From the history list you can:
  • View the full script and its metadata
  • Edit the script code and update it
  • Execute one or more scripts
  • Delete scripts you no longer need
Each entry shows the script title, language, linked manual test case (if any), who generated it and when.

​
Executing automation scripts

​
1. Select scripts to run

In the history list, use the checkboxes to select one or more scripts.

​
2. Click Execute

Click the Execute button. The scripts are queued and run via the Playwright service.
The Execute button is disabled while a run is already in progress. You’ll see an “Execution is in progress” indicator until it completes.

​
3. View results

Once execution completes, go to UI Test Runs to see pass/fail counts and download the full HTML report.

​
Tips for better automation

Prefer IDs (#elementId) or data attributes ([data-testid='login-btn']) over class names. These are less likely to break when the UI changes.
Each script should test one flow. Avoid combining unrelated actions — it makes failures harder to diagnose.
Instead of creating multiple scripts for similar flows, add multiple rows to the scenario table. The same script runs once per scenario with different data.

​
What’s next?

Execution History

View automation execution results and download reports

Running Tests Manually

Prefer manual execution? Here’s how