Start with one URL.

Everything you need to run your first real browser test, plus the concepts behind statuses, scope and evidence.

Guide · 01

Add an application

From the dashboard, choose Add application. Give it a name, a base URL and an environment type — development, staging, production or custom. Start with staging: it’s the safest place for your first tests.

  • Name and optional description
  • Base URL (https)
  • Environment type
  • Allowed domains and subdomains
Guide · 02

Authorise scope

Confirm you own the application or have explicit permission to test it, then list the domains Softsurance may visit. Requests to anything else — including private addresses — are refused by the worker.

Guide · 03

Run discovery

Discovery opens the homepage in a real browser and follows same-origin links within depth, page and time limits. It records titles, forms, controls, console errors and failed requests, and never submits forms. Progress is shown as it happens; it’s complete only when the backend says so.

Guide · 04

Approve tests

Each proposed test lists its category, steps, expected result, risk, confidence and whether it could change data. Edit, approve, reject or exclude it. Only approved tests can run.

Guide · 05

Schedule runs

Run now, once at a set time, every 15 minutes, hourly, daily, weekly, or on a cron expression — in your timezone. Overlapping runs are prevented where required, and skipped runs record why.

Concept

Execution statuses

Every execution ends in exactly one of nine states. The most important distinction is between FAILED (your app didn’t meet an assertion) and ERROR (our infrastructure failed).

StatusMeaning
PASSEDExecuted; every assertion held.
FAILEDExecuted; an assertion didn’t hold.
ERRORInfrastructure failure on our side.
BLOCKEDMissing credential or prerequisite.
INCONCLUSIVEEvidence doesn’t support a conclusion.

All nine statuses

Concept

Evidence

Each executed step can store a screenshot, assertion result, console output, failed requests and a DOM excerpt. Evidence is size-limited, retained per plan, redacted, and readable only by members of your organisation.

Reference

REST API

A versioned API under /api/v1/ will cover applications, discovery, tests, executions, schedules, issues and billing. Reference documentation will be published with the API.

Roadmap