Skip to Content
DocsOverview

WrightTest Docs

WrightTest is a UI test automation platform for creating, running, scheduling, and debugging browser checks.

It helps teams monitor important user flows, catch UI regressions, inspect failed runs, and keep browser checks running on a schedule.

What you can do with WrightTest

  • Create browser checks for critical user flows.
  • Record or edit test steps manually.
  • Run checks manually or on a schedule.
  • Use environments and variables like {{BASE_URL}}.
  • Review run results, screenshots, traces, and step-level errors.
  • Send failure and recovery notifications to Telegram or Slack.

If you are using WrightTest for the first time, start here:

  1. Install WrightTest
  2. Create your first browser check
  3. Configure environments and variables
  4. Debug failed runs

Core concepts

Projects

Projects group browser checks, schedules, environments, alerts, and run history.

Use a separate project for each product, service, or environment group you want to monitor.

Checks

A check is a browser flow made of steps such as opening a URL, clicking an element, filling an input, waiting for an element, or asserting page content.

Runs

A run is one execution of a check or suite. WrightTest stores the result, duration, screenshots, step status, and trace data when available.

Schedules

Schedules run checks or suites automatically using cron expressions.

Environments

Environments store reusable variables such as BASE_URL, USERNAME, or PASSWORD.

You can use variables in Start URL and check steps.

Alerts

Alerts notify your team when checks fail, recover, or pass, depending on the selected notification rules.

Troubleshooting

If something does not work as expected, start with Troubleshooting.

Common topics include failed browser runs, missing traces, screenshots, incorrect selectors, environment variables, and scheduled executions.

Installation