Record a test by using your site

For people who test a website but do not want to write test code: developers, QA and agency staff. SpinUI Recorder is a Chrome extension that turns what you do on your site into test steps.

The recorder is not in the Chrome Web Store yet. We send it to you with your account.

How it works

Connect the extension. Sign in to your SpinUI account from the extension. It works for your account and organization only.
Start on your site. Open the page you want to test and start recording. Chrome asks for access to that site, and you can remove it in Chrome at any time.
Use your site. SpinUI writes a step for each click, entry, selection, key press and page address. Sensitive fields are redacted in your browser, and you pick a stored secret in SpinUI instead.
Add checks and save. Add checks as you go, and accept or dismiss the checks SpinUI suggests. Saving turns the recording into a test in your organization.
Run it. Run the test on demand, on a schedule, from your pipeline or from a coding agent, in our cloud or on a runner you host.

What is included

One site at a time. Chrome asks for access to the site when you start recording on it.
Steps without code. SpinUI writes steps for your clicks, typing, selections, key presses and page addresses. Each element gets a main selector and backup selectors, so a test can still find an element when its main selector stops matching.
A clean window. Recording opens in a fresh private window by default, so your own logins stay out of the test. You can switch to your normal window in the extension options.
Sensitive fields are redacted. Password and hidden fields, and fields that look sensitive such as one-time codes, are redacted in your browser before anything is sent.
Checks while you record. Add checks as you go, and accept or dismiss the checks SpinUI suggests. You can also re-record a test to replace its steps.
Logic when you need it. Run steps only if something is shown, save text from the page as a variable, mark a step optional, or run a test once for each row of a data table. JavaScript steps cover what those cannot.

Plans. Every plan. Conditions, saved variables, optional steps and data tables are on every plan. JavaScript steps: Individual and up.

Good to know

Do not record pages with real card data. A card-number field without an autocomplete value is not redacted. The recorder takes no screenshots and does not read back your cookies or passwords, and Chrome does not encrypt the extension’s own storage, where your sign-in token is kept.

Questions

Do I need to write code to record a test?

No. You use your site and SpinUI writes the steps. When a flow needs logic, tests support conditions, saved variables, data tables and JavaScript steps (Individual and up).

Is the recorder in the Chrome Web Store?

Not yet. We send the extension to you with your account, and this page will say when it is listed.

Does the recorder capture my passwords?

No. Password and hidden fields, and fields that look sensitive such as one-time codes, are redacted in your browser before anything is sent. You choose a stored secret in SpinUI instead. A card-number field without an autocomplete value is not redacted, so do not record pages with real card data.

What happens when a selector stops matching?

Each element gets a main selector and backup selectors, so a test can often still find it. If a step still fails, AI can suggest a new selector (on plans that include AI), and you promote it or dismiss it. You can also re-record the test.

Which browser runs a recorded test?

You record in Chrome. Cloud runs use Chromium. On a private runner you host, Firefox and WebKit are available where you install them.

Keep reading

Check your site the way a person would

Record your first test by using your site.

Contact us Sign in