SUNRISE INVENTIVE
04 For teams too small to have a testing department Early access · free first year

Autotest Forge

Give it your website and a login. It works out what to test, tests it, and tells you what broke.

Request early access
The problem

After every change, someone should click through the site and check that the old things still work. It is dull, it takes hours, and it is the first thing dropped when a release is due. So it gets skipped, and a customer finds the broken checkout instead.

What changes

The clicking happens automatically, every time, in a real browser. You did not have to write the checks — it worked them out by looking at your site. When something fails you get the screen it failed on, so you are not guessing.

How it works

STEP 01

It looks around

Give it the address and a login, and it maps the pages and forms your customers actually use.

STEP 02

It writes the checks

Not just the happy path — what happens with the wrong password, an empty field, a stupid value.

STEP 03

It runs them

All of them, or a quick set before a release. In a real browser, so the result means something.

STEP 04

It shows you the failure

A picture of the screen where it went wrong, and a one-click repeat once you think it is fixed.

AutoTest Forge dashboard

Catch it before customers do

Run it on every change, overnight, or before a release. It does not get bored and it does not skip the boring page.

It also checks the locks

While it is on your site it flags common security mistakes — the sort found by anyone who goes looking.

Nothing leaves your network

It can run entirely inside your own environment, and it does not keep your passwords.

Autotest Forge demo
Watch on YouTube — a website in, a finished test run out