Run in our cloud, or inside your network
For teams that test public sites and for teams whose sites sit behind a VPN or on an intranet. Run tests in our cloud, or on a runner you install inside your own network.
How it works
- Choose where a suite runs. On a suite or an environment, set Runs on to the SpinUI cloud or to one of your runners. A suite can only use runners of its own organization.
- Cloud: nothing to install. Runs start in our hosted service in the United States, using Chromium.
- Private: register a runner. In Settings, Runners, register a runner and copy its one-time token. Install it on a Windows computer as a service, or with Docker. It shows as online within a minute.
- It asks for work. The runner connects out to SpinUI over HTTPS, takes work addressed to it, runs the browser on your computer and sends the results back.
What is included
- Cloud runs. They use Chromium and run in our hosted service in the United States. Tests run inside SpinUI cannot reach private or internal addresses.
- Private runners. A private runner is a small service you install on your own computer or server, on Windows or with Docker. It connects out to SpinUI over HTTPS, so you open no inbound ports.
- Your network. A private runner sees what its computer sees, so it can test an intranet or a staging site behind a VPN. It receives the secrets a test needs only for that run, and keeps them in memory.
- More browsers. A private runner can run Firefox and WebKit as well as Chromium, where you install them.
- No cloud minutes. Runs on a private runner do not use your included cloud minutes.
- Evidence for every run. Each run keeps screenshots and a trace; video on paid plans. How long they are kept depends on your plan.
- Updates and control. A Windows runner installed as a service updates itself, and only while no test is running. You can revoke a runner at any time, and it stops within seconds.
Plans. Cloud runs: every plan. Private runners: Team and Business.
Good to know
Cloud runs are Chromium only. Firefox and WebKit are not available in the cloud. During the private beta the Windows runner is not code-signed, so Windows may warn about an unknown publisher. A runner started from a console, and a Docker runner, do not update themselves.
Questions
Do I need to open ports for a private runner?
No. The runner only makes outbound HTTPS connections to your SpinUI address. It never opens a listening port. Plus whatever the sites under test need, of course.
Can a cloud run test my intranet or a staging site behind a VPN?
No. Tests run inside SpinUI cannot reach private or internal addresses. Use a private runner inside your network for those sites.
What can a private runner see?
What its computer can see, so intranet pages too. It receives the test definition and the secrets that test uses, only for that run and only in memory. It cannot see SpinUI’s database, other customers’ data or other organizations’ runners. Its credential is limited to your organization.
Do private runs use my cloud minutes?
No. Runs on your own runners use no cloud minutes.
Which plans include private runners?
Private runners: Team and Business. The pricing page has the full comparison.
Keep reading
Check your site the way a person would
Record your first test by using your site.
Accounts are opened on request for now. Contact us and we will set one up.