Browser tests

A browser test (a UI test) is a list of steps — type here, click there, check this — that TestBrick replays in a real browser in the cloud.

How it works

Describe — tell Bricklayer what to test in plain words
Watch — it builds the test in a live browser while you watch, and asks when it’s unsure
Confirm — you pick the checks that prove the flow worked, and the first replay proves the test runs on its own
Run and monitor — run it any time, or let a monitor run it on a schedule
Understand failures — a failed run opens with why it failed

A saved test

What a test can do

Step	What it does
Type	Types text into a field — fixed, new each run, or a stored secret
Click	Clicks a button, link, checkbox or any element
Select	Picks an option from a dropdown
Press a key	Enter, Tab, Escape and so on
Upload a file	Attaches a file to an upload field
Wait	Pauses for a few seconds
Check	Checks the page shows some text, is on some address, or that two numbers add up
Emails	Waits for an email and uses the code or link in it — see Email & codes
Authenticator code	Types a fresh 2FA code from a stored key — see Secrets & 2FA
Remember a number	Reads a number (like a balance) to compare later in the same run

Where tests run

Every run happens in TestBrick’s cloud browsers, so it behaves the same whether you click Run, a monitor starts it, or a teammate re-runs a shared result. You can watch any run live.