VALIDATE · MANUAL TEST DISPLACEMENT

# Your manual test scripts are already written. Make them run.

The cheapest automation project is the one where the source material exists. Manual scripts are English instructions, which is exactly what the agent takes as input.

Import CSV or XLS

No selector code

Weeks, not quarters

## WHO THIS IS FOR

QA managers with a regression suite measured in person-weeks

## HOW IT WORKS TODAY

A regression cycle is a staffing plan. Automating it has been quoted as a rewrite into selector code, at a cost that never cleared the business case.

## How it works

### The agent does what the person does.

01

#### Import the existing suite.

Text, CSV or spreadsheet. The steps a tester follows are the steps the agent follows.

02

#### Run it and review what it did.

Each step is traced with the screenshot that justified the action, so a reviewer can check the agent's reasoning.

03

#### Keep the file in version control.

The suite becomes markdown in your repository, diffable in a pull request.

## WHAT A RUN LEAVES BEHIND

Every run ends in something you can hand over.

An executable suite from the documents you already own

A step report per run

Version-controlled files, no proprietary store

## WHERE THIS IS THE WRONG TOOL

### The limits, stated up front.

Scripts that assume tribal knowledge need that knowledge written down first

Exploratory testing is a human activity and stays one

We publish the limits because a claim you can check is worth more than one you cannot.

## WHERE IT LANDS

**Rail & Transportation** Ticketing, dispatch and passenger systems  
**Financial Services** Terminal emulators, trading desktops, Citrix  
**Insurance** Policy admin and claims desktops  
**Medical Devices & Health** Device displays and clinical workflows

## NEXT STEP

### See it on your own systems.

We scope the trial with you and run it on your real environment. A person answers, within one business day.