How to record your first UI autotest

Teams postpone automation not because they doubt its value, but because the classic path is expensive: frameworks, locators, code maintenance, and separate automation expertise. TestManager lowers that barrier: Recorder captures a real user flow, and the platform turns it into a managed test case with environments, Page Objects, run history, and reporting.

Step 1. Capture a business-critical scenario

Start with the user path that matters for release confidence: login, request creation, payment, account flow, or a key form. In TestManager, choose the workspace and project where this scenario will live as part of the shared test base.

Strong automation starts with the right model: a scenario should be clear for QA, transparent for management, and structured enough to survive interface changes.

Step 2. Choose the recording mode

TestManager Recorder supports two practical workflows. Page Object mode helps build a managed library of page elements and locators. Test Case mode records the sequence of user actions: navigation, clicks, input, keyboard actions, waits, and checks.

1

Open the page you want to test

2

Start TestManager Recorder

3

Choose Page Object or Test Case mode

4

Click Start recording and run the scenario like a real user

5

Add Verify or Wait steps from the recorder panel when needed

6

Stop recording and export JSON

Step 3. Review steps before import

After recording, the scenario is not a black box. It remains an editable structure. You can reorder, delete, or refine steps: action type, locator, input value, wait, or assertion. This matters for dynamic interfaces where locator quality directly affects regression stability.

JSON fragment for test-case import

1{

2  "steps": [

3    { "step_number": 1, "step_type": "NAVIGATE", "data": { "url": "https://app.example.com/login" } },

4    { "step_number": 2, "step_type": "PAGE_OBJECT", "data": { "element": { "title": "Email", "locator_type": "XPATH", "locator_value": "//input[@name=\"email\"]" }, "action": { "type": "INPUT_TEXT", "value": "user@test.com" } } },

5    { "step_number": 3, "step_type": "VERIFY", "verify_type": "ELEMENT_VISIBLE", "verify_selector": "//h1[contains(., \"Dashboard\")]" }

6  ]

7}

Step 4. Import JSON into the test-case editor

Create a test case in the UI testing section and import the JSON from Recorder. TestManager validates the steps, maps elements to Page Objects, and adds the scenario to the table. After that, the case can be enriched with tags, priority, preconditions, waits, checks, and test files.

Step 5. Select an environment and run the test

Before the run, choose the project environment and execution parameters. TestManager creates a test run, stores the history, and opens a report with every step, duration, errors, and related artifacts. The autotest becomes not a private script, but a clear management tool.

4/4

passed

Time

12.8s

Environment

Project environment

Status

PASSED

What to do after the first run

One test case is only the start. You can organize it into folders, combine it with other cases into a test plan, run it repeatedly in the right environments, and analyze history. The same interface keeps Page Objects, tags, archive, run reports, and API collections for OpenAPI/Swagger scenarios and run configurations.

How to record your first UI autotest in TestManager without code