Everything you might ask,
in plain words

Assertline checks that your website still works, so you do not have to click through it by hand every time something changes.

You go through your website once, the way a customer would: open a page, sign in, add something to the basket, pay. Assertline remembers every step. From then on it can repeat those steps for you whenever you like and tell you whether everything still works.

No. You record a test by using your website normally, and you run it by pressing a button. There is nothing to write and nothing to install on your website.

Anyone responsible for a website or web application working properly: shop owners, product managers, testers, support teams and developers. If you have ever found out from a customer that a page was broken, it is for you.

Yes, there is a Free plan and it does not need a payment card. It covers up to 3 people and 2 projects, with as many tests as you like, run on your own computer.

The paid plan, Pro, adds running tests on our computers, more history and team features. See pricing.

• A computer with the Google Chrome browser.
• An email address. You can sign in with Google, or with your email and a password.
• The website you want to test.

You cannot record a test on a phone or a tablet.

A test is one journey through your website that you recorded, for example "a customer buys a product". It is a list of steps (open this page, click this button, type this text) plus the things you asked Assertline to check along the way.

1. Go to app.assertline.com and create your account: sign in with Google, or register with your email and a password. This creates your free workspace.
2. Create a project. A project is one website you want to test.
3. Add the Assertline Recorder to Chrome (see the next question).
4. Record your first test, then press Run.

The dashboard shows these steps in a "Getting started" list and ticks them off as you go.

The recorder is a free add-on for the Chrome browser called Assertline Recorder. It is being reviewed by the Chrome Web Store at the moment. As soon as it is approved, the link to add it will be on this page and in your dashboard.

1. Open your website in Chrome.
2. Click the Assertline Recorder icon, choose your project and press Start.
3. Use your website as a customer would.
4. Press Stop when you are done.

The test is saved to your workspace straight away. Only the tab you started on is recorded, and only until you press Stop.

A check is something you ask Assertline to confirm while the test runs. For example: "the words Order confirmed are on the page" or "the Pay button is visible". Without checks a test only confirms that the steps can be done. With checks it also confirms that the right thing happened.

You add a check while recording, from "Add check" on the recorder's toolbar.

A few minutes. Recording a test takes as long as going through your website once.

Yes. Register with your email address and a password. We send you an email with a link to confirm the address, and you are in. If you forget the password, "Forgot password" on the sign-in page sends you a link to set a new one.

Look in your spam or junk folder first; it comes from no-reply@assertline.com. If it is not there, sign in and press the button to send it again. The link works for 24 hours.

Open the test in the dashboard and press Run. You choose where it runs:

• In your own Chrome. The test opens in a new tab and you can watch it. Free.
• On your own computer, in the background. The Assertline desktop app (Windows and Mac) runs tests without getting in your way. Free.
• On our computers. Nothing of yours needs to be switched on. Part of the Pro plan.

Every run has a results page. It shows each step with a clear passed or failed mark and how long it took. If a step failed, it tells you which one and why, so you know where to look.

Yes, with the desktop app (Windows and Mac). You pick a test and how often it should run, and the app runs it in the background while your Mac is switched on. Development teams can also start tests automatically from their release process, which is part of Pro.

On the Pro plan, Assertline can post finished runs to a Slack channel. There are no email alerts yet.

People in your workspace can open the same results page. For anyone else, export the results as a PDF from the results page.

Yes. Give tests a label, for example "checkout", and run every test with that label in one go. This is called a batch, and you get one overall result for it.

About as long as it took you to do the same steps. Most tests finish within a minute or two.

Yes. On the "Create with AI" page you write what to test in plain words, for example "sign in, add a product to the cart and check it is in the cart". An AI agent then does it in a browser, step by step, and records each step as a normal test. You watch it work, and nothing is saved until you have looked at the steps and pressed Save.

In the desktop app it uses a browser on your own computer that you can see, so it can reach the same websites you can, including ones on your office network. On the Pro and Enterprise plans it can also work in a browser on our computers, straight from the dashboard with nothing to install. That one cannot reach websites on a private network.

An OpenAI key. An owner or admin of your organization adds it once under Settings, in the AI agent section. Assertline checks the key when you save it and never shows it again. OpenAI then bills you for what the agent uses; we charge nothing for it.

You give each private value a name, such as LOGIN_PASSWORD, and write the name in your instruction like this: {{LOGIN_PASSWORD}}. The agent types the real value into the page. The AI is told only the name, and the saved test keeps the value locked away. One thing to know: the AI looks at pictures of the page, so something typed into an ordinary box, like a user name, is visible to it there. A password box hides what is typed.

Yes. Stop ends the run at once and takes you to the steps recorded so far. You can also type a message to the agent at any time, and it reads it before its next step. When it is not sure, or something did not work, it pauses and asks you.

It cannot get past a "prove you are human" check or a code sent to your phone. In the desktop app it pauses so you can do that part yourself in its browser, then you press Continue. In the cloud nobody can click in its browser, so use the desktop app for such a site. Some websites, large public ones especially, refuse automated browsers altogether. It also does not record steps inside a page embedded within another page.

Small changes are usually fine. Assertline remembers several different ways to find each button and field, so if one stops working it uses another, and the results page tells you it did.

If a step really cannot be done any more, for example a button was removed, the test fails and shows you which step. That is the test doing its job.

The most common reasons:

• The words or the layout changed, so a check no longer matches. Update the check, or record the test again.
• The page was slower than usual. Run the test again.
• The test uses something that only works once, such as a discount code or a new email address.
• The website refused an automated visitor (see "bot protection" below).

The results page shows the failed step and the reason.

Yes. In the dashboard you can remove steps, change their order and change the details of a step. For bigger changes it is usually quicker to record the journey again.

Some websites refuse visitors that are not people. When Assertline runs a test on our computers, it says honestly that it is an automated browser, and such a website may turn it away. Assertline reports that as "blocked". It never pretends the test passed.

The fix is to run that test in your own Chrome or with the desktop app. If the website is yours, your technical team can also let Assertline through.

Yes. Sign in while you record, and Assertline signs in the same way each time the test runs. The password you typed is stored locked (encrypted) and is never shown again, not even to you.

Use a test account for this, not your personal one.

Yes. Run the test in your own Chrome or with the desktop app, and it reaches whatever your computer can reach, including a private or internal website. Tests that run on our computers can only reach public websites.

It can run a test at phone and tablet screen sizes, so you see how the mobile version of your website behaves. It does not use a real phone, and it does not test mobile apps from an app store.

You record in Chrome. On the Pro plan you can run the same test in Edge, Firefox and Safari's engine through a service called BrowserStack, using your own BrowserStack account.

• Pass a "prove you are human" puzzle (captcha).
• Use one-time codes sent by text message or email, because a code only works once.
• Record inside an embedded frame, such as some payment forms supplied by another company.
• Upload your real file again. When a test repeats an upload, it uses a stand-in file with the same name.
• Test mobile apps or desktop programs. It tests websites.

Yes. If your designs are in Figma, you can connect the file and ask Assertline to compare a part of the page with its design: colours, text styles, sizes and the spacing between elements.

Your tests and results belong to your workspace, and only the people you invite can see them. Passwords and other secrets are stored encrypted and are never shown again. Everything travels over an encrypted connection.

Only the tab you start recording on, and only between Start and Stop. It notes what you click and type and what the page loads, because that is what the test repeats. It does not watch your other tabs or your browsing.

Assertline recognises passwords, card numbers, card security codes and one-time codes. They are stored encrypted under a name, and the test keeps only that name. Nobody can read them back in the dashboard, including you.

We still recommend test accounts and test cards, not real ones.

It depends on where the test runs:

• With the desktop app: on your own computer. They are not sent to us, unless you are on Pro and choose to upload them so your team can see them.
• In your own Chrome: they are sent to Assertline and stored with the results, so the results page can show them.
• On our computers (Pro): they are stored with Assertline.

On Amazon Web Services servers in the United States.

It depends on your plan:

• Free: 30 days. A test and its results are removed 30 days after the test was recorded.
• Pro: 1 year.
• Enterprise: no limit.

You can save your tests to a file at any time from Export / Import in the dashboard.

Deleting a test or a project in the dashboard removes its data. To close your account completely, write to us from the Support page in the dashboard.

Yes. Download it only from assertline.com/download. The Mac version is signed by us and checked by Apple (notarized), so your Mac opens it without a warning. The Windows version is new and its Windows certificate is still on its way, so Windows asks you to confirm before it opens: choose More info, then Run anyway.

Free is for trying Assertline and for small projects: up to 3 people, 2 projects, tests run on your own computer, 30 days of history.

Pro costs $29 for each person a month, or $24 a month when paid yearly. It adds running tests on our computers, unlimited people and projects, Slack alerts, other browsers and 1 year of history. The full list is on the pricing page.

No. The Free plan needs no card and has no time limit.

No. Tests run in your own Chrome or with the desktop app are free and unlimited on every plan, because they use your computer.

A hosted minute is one minute of a test running on our computers. Pro includes 100 hosted minutes for each person every month, shared by the whole team.

If you use them up, extra minutes are paid from credits, which you buy in advance in packs of $10, $25, $50 or $100. Nothing is ever charged automatically. If you have no credits left, tests simply run on your own computer.

Yes, from Settings in the dashboard. Your plan stays active until the end of the period you paid for, and then your workspace moves to the Free plan.

They stay in your workspace and keep working. The Free plan's limits apply from then on: you cannot add more than 3 people or 2 projects, and tests and results older than 30 days are removed.

Payments are handled by Paddle, a payment company that sells Assertline on our behalf. Paddle's name is on your invoice, and it adds the right tax for your country. Refunds are explained in the refund policy.

Open Settings in the dashboard and invite them by email address. Assertline emails them an invitation. They open the link in it and sign in with Google or choose a password.

Yes. There are three roles. The owner and admins manage people, payment and settings. Members record and run tests.

Yes. Create a project for each website. The Free plan includes 2 projects; Pro has no limit.

It runs your tests on your own computer in the background, also on a schedule, and shows the dashboard in its own window. It is free on every plan. You do not need it to record or to run tests in Chrome.

Both. You get it from the download page: one download for Windows 10 and 11, and one each for Macs with an Apple chip and Macs with an Intel chip. The Windows version is the newer of the two. Until its Windows certificate arrives, Windows asks you to confirm when you open it (choose More info, then Run anyway), and it does not yet update itself.

On a Mac it updates itself: when a new version is ready you get a notice, and it is installed the next time you quit the app. The Windows version does not do this yet: get the newer version from the download page and install it over the old one.

Write to support@assertline.com, or sign in to the dashboard and open Support. Write what happened. You get an email confirming we received it, and a person replies to the email address of your account.

Yes. Assistants such as Claude can connect to Assertline, run your tests and tell you what failed. In the assistant, add a connector with the address https://app.assertline.com/api/mcp; your browser opens Assertline, you sign in and allow it. The assistant can find tests, run them and read results. It cannot change or delete anything, and you can remove it under Settings, Connected apps. Details are in the API and MCP guide.