01 / Overview
Continuous testing for production softwareRef. QA-01Software quality. On autopilot.
Independent, always-on checks of your web app — with no tests to write. Catch regressions and see exactly why they failed, before your users do.
- WAITHeading “Software quality. On autopilot.” is visible—
- WAITDocument title is set—
- WAITButton “Get a free report” is visible and enabled—
- WAITLink “Explore platform” resolves—
- WAITNo horizontal overflow at this width—
- WAITNo script errors since load—
02 / Problem
Why tests stop getting written§ 02.0We build for the team that knows what should be tested and never has the hours to keep it tested.
A test suite is only as good as the last time someone maintained it. Softsurance keeps testing after people stop.
Coverage decays quietly.
New pages ship without tests. Old tests break on a renamed selector and get skipped. Nobody decides to stop testing — it simply stops.
A red build is not an answer.
Knowing that something failed is the easy part. The hours go into finding the screenshot, the console line and the request that returned 500.
Users find it first.
Without a recurring check against staging and production, the first report of a broken checkout is a support ticket.
03 / How it works
Three steps, no test codeSetup in minutesPaste a URL. Approve what we find. It keeps checking.
Nobody on your team writes, runs or maintains test code. You stay in control of what runs.
Paste your URL.
A real browser reads your staging or production site — every page, link, form and button — without clicking, typing or submitting anything.
Approve what we propose.
Softsurance turns what it found into plain-language tests. You approve the ones that matter; nothing runs until you do.
It keeps checking.
Tests run daily, hourly or after each deploy. When your UI changes, updated tests are proposed for you — nobody maintains a test suite.
04 / Why Softsurance
How it compares§ 04.0Not another tool for writing tests. An independent check.
How Softsurance compares with writing tests yourself and with the AI in your editor.
| Writing tests yourself | AI in your editor | Softsurance | |
|---|---|---|---|
| Who writes the tests | Your team | Your team, with AI help | Softsurance proposes them — you approve |
| When the UI changes | Tests break until someone fixes them | Someone asks the AI to fix them | Updated tests are proposed for you |
| When something breaks | A red build | Only when someone asks | Screenshot, trace, console and the likely cause |
| Who checks the work | The people who wrote the code | The tool that wrote the code | An independent check |
05 / Products
What Softsurance tests5 modulesFive ways in. One evidence record.
UI testing ships first. API, database and end-to-end workflow testing follow on the same evidence record.
UI testing
Real browsers, real pages, recorded evidence.
Release 102API testing
OpenAPI import, status and schema assertions.
Preview03Database testing
Read-only schema and integrity checks.
Roadmap04End-to-end workflows
Structured journeys with approval gates.
Roadmap05AI investigation
Evidence-grounded failure reports.
Preview06 / Console
The execution recordEvidence viewOne failure, and everything you need to read it.
Assertions, screenshots, console output and failed requests stay together, so whoever is debugging starts with facts instead of a search.
07 / Method
From URL to evidenceHuman-approvedWhat happens between your URL and a result.
Five stages. Nothing executes until a person has approved it, and nothing leaves the scope you set.
Discover
Playwright loads the target, follows same-origin links within depth and page limits, and records pages, forms and errors. Nothing is submitted.
Gate · scopePlan
Sanitised findings become proposed tests in a validated schema. Without an AI provider, deterministic templates are used.
Gate · schemaApprove
You edit, approve, reject or exclude each proposal. Anything that could change data needs explicit approval.
Gate · humanExecute
Approved tests run in an isolated worker as a restricted action set. No AI-written code is ever executed.
Gate · policyInvestigate
Failures are analysed against the evidence actually captured, with facts and hypotheses kept apart.
Gate · evidence08 / Continuous
Deterministic schedulingTimezone-awareSet the cadence once. It keeps running.
Schedules live in the database and run through a real task queue — never a browser timer, and never an AI deciding whether to run.
Also hourly, daily, weekly, once, or a custom cron expression.
Duplicate-run protection when a single active execution is required.
Every skip records why: limit reached, overlap, or schedule paused.
Retries are bounded and recorded. Flaky tests are shown, not hidden.