Text2Test Logo
Request a Demo

Write It Once. Let Autopilot Figure Out the Rest.

T2T Autopilot takes your plain text instruction and hands control to an LLM. It reasons through the flow, navigates dynamically, and executes without rules or compilation. Copy, paste, run.

Request a Demo
How It Works

Plain Text In. LLM Takes Control.

With T2T Autopilot you write the test instruction in plain text exactly as you would describe it to a colleague. No syntax. No selectors. No step-by-step breakdown required. You paste it in, and the LLM takes it from there.

It reads the screen, reasons about the flow, and executes the steps dynamically. If something on the page looks different than expected, it adapts. It does not fail on a missing class name.

Slackcan someone check if the discount code still works at checkout?
JiraUser should be able to reset password from login screen
FigmaOn mobile, tapping the menu icon opens a drawer from the left
EmailThe export button doesn't seem to work for CSV files over 10mb
Paste any of these into Autopilot. It runs.
What You Get

Everything T2T Autopilot Does for You

Plain Text Input

Write your test instruction in plain text exactly as you would describe it. No syntax, no selectors, no step-by-step format required.

Reasoning Over Rules

Instead of executing a fixed script, the LLM reasons about what is on screen at each moment and decides what to do next.

Adapts to UI Changes

When a class name changes or an element looks different, Autopilot recognizes the intent and continues. Rule-based tools stop. Autopilot keeps going.

Copy and Paste

Take a description from a Jira ticket, a Slack message, or a spec, paste it into an Autopilot sequence, and run. No reformatting needed.

Conditional Flow Handling

Flows that branch based on data or user state. Multi-step wizards. Anything where the path depends on what is shown on screen.

Hard-to-Predict States

When the UI depends on time, history, or external data, scripts cannot keep up. Autopilot reads the current state and acts on it.

Mix With Other Sequence Types

Combine Autopilot with T2T Native, Script Injection, Visual Verification, and HTTP Requests in a single test case. Use each where it fits best.

End-to-End Execution

From interpreting the instruction to clicking the final element, the LLM handles the full flow without manual intervention or pre-built scripts.

Best for Exploratory Testing

Right tool for edge cases, hard-to-predict flows, and tests where reasoning matters more than fully deterministic, repeatable results.

Test case sequences

One Test Case. Five Ways to Build a Step.

A test case in Text2Test is not a single instruction type. It is a sequence. Each step can be a different prompt type, combined in any order to match exactly what you need to test.

T2T Native

Write the steps in plain text. Text2Test Native reads the screen semantically and executes. No selectors, no DOM knowledge required.

Script Injection

Paste an existing script or auto-generate one and run it inline within the test. For when you need precise programmatic control at a specific step.

T2T Autopilot

Hand control to AI for complex flows that need reasoning. Autopilot navigates the product autonomously and hands back when done.

Visual Verification

Take a screenshot diff or check element visibility at any point in the sequence. Catches layout regressions and UI changes.

HTTP Request

Call an API and assert on the response. Combine with UI steps to test the full stack in a single test case.

Mix and build in any order. A test case can start with a T2T Native step, run an HTTP request to set state, verify visually, inject a script for a specific action, and hand off to Autopilot for the final flow. All in one sequence.

FAQ

Common Questions

See Autopilot Handle a Flow You Thought Needed a Script

Request a demo and we will show you T2T Autopilot running a real complex flow from a single plain text instruction. No script. No selectors. Just reasoning.

Request a Demo