Get started with Verify

Test your app like a user would

Verify opens your app in a browser, tries real user tasks, and shows you what worked and what broke. You can watch it work and replay the results.

Start with a website URL. You don't need a repository or test scripts. Check your workspace’s included browser minutes and billing details before starting a run.

1 Add your app and explore it

1. Open Verify and add a project for your app.
2. Add the URL you want to test, such as your staging site. This is your environment.
3. If your app needs a login, add a test account. Use an account with data you are comfortable changing.
4. Start Discovery. Tell it which parts of your app to explore and what it is allowed to do.

Discovery explores your screens and user flows, then suggests tests. You can watch its browsers while it works.

Testing an app behind a VPN? Connect your private network first.

2 Run your first test

Open Scenarios in your project. A scenario is a saved test, such as “A customer can add an item to their cart.”

Review the tests Discovery created, or write your own. Describe what the user should do and what should happen. Select a test, choose an environment, and run it.

For recording a journey or connecting tests across personas, see recording and Scenario dependencies.

Need to test a signed-in flow? Follow the login testing guide.

3 See what happened

Open the run to see its result and replay what the browser did.

• Passed: the tested outcomes worked.
• Failed: something did not match the expected result. Open the finding to see the evidence.
• Blocked or inconclusive: Verify could not finish or confirm the result. Read the reason, fix the setup if needed, and try again.

A passing run covers the tests it ran. It doesn't mean every part of your app has been tested.

Test pull requests automatically

Once you have tests you trust, connect your repository in PR Testing. Choose when tests run and where the preview URL comes from. Verify tests relevant scenarios against the preview and posts the results to your pull request.

Set up GitHub preview testing or connect GitLab.

For file triggers, events and schedules, see the Verify reference.

Look for more bugs

Use Deep Scan when you want Verify to investigate beyond your saved tests. Give it a goal, such as “Check whether customers can cancel a subscription.”

Tell it what it may change and how long to spend. Review the findings and replay the evidence before deciding what to fix.

Keep your project ready

• Knowledge holds what Verify has learned about your app. Add any instructions or context it should know.
• Environments holds the versions of your app you test, such as staging or a PR preview.
• Credentials holds your test accounts.

Prefer your terminal or coding agent?

Install the CLI to run tests from your terminal, or connect your coding agent. You can also write scenarios as files and keep them in your repository.

See the scenario reference for test files and the CLI reference for commands, uploads, and local runs.

Testing a desktop or mobile app?

Choose Computer use when creating your project. These tests need a supported desktop image or mobile app build instead of a website URL. Read about supported environments, or see iPhone app setup.

For detailed setup, fixtures, schedules, recordings and supported app types, use the Verify reference.

Archive old runs

In Scenarios → Runs, administrators can choose Archive on a finished run to hide an obsolete attempt from normal history. Select Status: Archived to find it again and choose Restore. Its original outcome, recordings, billing and cleanup records remain available, including through existing run links. Active runs must finish or be cancelled before archiving.

Computer-use recordings

The recording's Events lane links native evidence reviews to their recorded capture times. Phases shows when computer-use actions ran. Older recordings without action names use numbered action labels; these timings do not claim that an authored step or outcome passed. Drag the timeline to preview a position, then release to seek precisely. Recently viewed clips stay available when jumping back and forth.