You write the steps the way you would explain them to a colleague, in your own language. Line by line or all in one go. Text2Test Native reads it either way. No selectors. No XPath. No DOM knowledge. If a human can follow the instruction, Text2Test Native can run it.
The model looks beyond the happy path. It asks:
That reasoning is built in. You don't have to prompt for it.
Text2Test Native uses specialized AI models for software testing. Instead of parsing HTML or querying the DOM, it reads the screen semantically and visually, the way a human tester does. That is why a renamed class, a refactored component, or a moved button does not break the test.
A selector changed. A class got renamed. A div got wrapped in another div. Same product. Same behavior. Text2Test Native still finds the element because it reads what things mean, not where they live in the DOM.
When you write "Click Submit and verify the confirmation screen appears", Text2Test Native executes that against what the user actually sees. If Submit stops working, the test fails. If a designer renames the button class, the test keeps passing.
Every other tool patches the selector problem. Text2Test Native removes it. The behavior is the test. The code is irrelevant.
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.
Write the steps in plain text. Text2Test Native reads the screen semantically and executes. No selectors, no DOM knowledge required.
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.
Hand control to AI for complex flows that need reasoning. Autopilot navigates the product autonomously and hands back when done.
Take a screenshot diff or check element visibility at any point in the sequence. Catches layout regressions and UI changes.
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.
Stop treating test case generation as a separate task. Every time you describe what your product should do, Text2Test Native turns it into coverage that stays honest as the product evolves.
Request a Demo
