Text2Test Logo
Request a Demo

See Exactly What Changed. Catch It Before It Ships.

Upload a reference screenshot. Describe what should match in plain text. Text2Test compares the current screen against your reference and tells you whether it does. No pixel thresholds. No assertion code. Just your words and a visual truth.

Request a Demo
How It Works

Upload a Reference. Write What Should Match.

Upload a reference screenshot directly into the Visual Verification sequence step. Then write a plain text prompt describing what you want to check. Text2Test compares the current screen against your reference and asserts whether the visual conditions you described are met.

No configuration needed. You just describe:

Are the button colors consistent with the reference?
Is the page layout the same as the reference?
Is the navigation bar positioned correctly?

No pixel thresholds. No config files. Just describe what you expect to see.

Visual Verification reference upload and plain text prompt in Text2Test
Visual regressions

Catch what your other tests cannot see.

A button can be technically clickable and visually broken at the same time. Logic-based tests check behavior. Visual Verification checks appearance. Use both in the same test case to get complete coverage.

Logic tests check behavior

A logic-based test confirms the button is clickable and the action fires. It says nothing about whether the button is the right color, the right size, or even visible in the layout.

Visual Verification checks appearance

Layout shifts, color changes, missing elements, broken spacing, overlapping components. Visual Verification flags any difference between the current screen and the reference.

Use both for complete coverage

A single test case can run T2T Native steps for interaction, then a Visual Verification step to assert the screen looks exactly as expected after each action. Behavior and appearance, in one flow.

Test case sequences

One Step in the Sequence. Works Alongside Everything Else.

Visual Verification is one of five sequence types in Text2Test. Add it at any point in a test case. After a form submission, after a page transition, after an API call. It slots in wherever you need a visual check.

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 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

Compare the screen against a reference image or a baseline screenshot. Catches layout shifts, color changes, and broken spacing.

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.

Plain Text Prompts

Describe What Your UI Should Look Like

01

Button and color checks

"Are the button colors consistent with the reference screen?" Catch color drift and inconsistent styling after a deploy.

Plain text prompt
02

Layout and structure

"Is the overall page layout the same as the reference?" Spot layout shifts, broken spacing, and misaligned sections.

Plain text prompt
03

Navigation and positioning

"Is the navigation bar visible and positioned correctly?" Verify that key elements stay where users expect them.

Plain text prompt
04

Component-level checks

"Does the checkout summary match the reference design?" Assert a specific component against a known good state.

Plain text prompt
FAQ

Common Questions

Add a Visual Check to Any Test in Seconds

Request a demo and we will show you Visual Verification running inside a real test case.

Request a Demo