Automated website testingSet up by clicking, not coding
Click through your website once, the way a customer would, and say what should be true on each page. BitAssure walks the same path again in a real browser as often as you like, and tells you in your own words what still holds and what broke.
No card needed.
- The total reads $1,250.00
- Pay now is enabled
- The delivery date is shownFound an empty space instead, 0:34 into the video
Real Chrome, every night at 02:00, and from your pipeline on each release.
The parts of a website that break without anyone noticing
A deploy that passed its own tests can still leave sign-in broken, a total wrong or a button that does nothing. These are the checks that catch that, each one a sentence somebody wrote.
The dashboard shows "Welcome back"
Signing in still works
Record the sign-in once. Every other journey can start from it, so it is never recorded twice and a broken login shows up first.
The order number is shown
Checkout and forms go through
Typing, dropdowns, dates, switches and the "Are you sure?" box all count as steps, so a whole form is walked the way a customer fills it in.
The total reads $1,250.00
Prices and totals are right
Exactly a figure, or containing the part you care about. A total that silently changed is the failure customers notice first.
Pay now is enabled
Buttons can be used
Enabled or disabled at the right moment, on or off. "Pay is disabled until an amount is typed" is a check, and so is the opposite.
Testing software for the whole team, not only the developers
Nobody writes a script, so the person who knows how the website should behave is the person who sets the checks. Developers keep their own tests; this covers the paths a customer takes.
Real Chrome, at your address
Your staging or production site opens in a real Chrome browser. Nothing about your site has to change, and there is nothing to install on it.
On a schedule, or from CI
Hourly, daily, every weekday or weekly, on every plan. Or start a run from your build pipeline with an API key, and read the results as JUnit in GitHub Actions or any CI.
A video of every run
Each run is recorded, and every check is marked at the moment it was judged. When something fails, you watch it fail instead of trying to reproduce it.
A report anyone can read
Pass or fail, screen by screen, in the sentences your team wrote, as a page or a PDF to hand to a manager, a client or an auditor.
Sites inside your network
Staging behind a VPN or an intranet is reached through a small connector you run on a machine inside it. It calls out to us, so nothing on your side has to be opened.
Easy to put right
A check that fails because the page changed, not because it broke, is fixed in place. It keeps its wording and its history, and the rest of the journey stays recorded.
What it does not do, so you can plan around it
- Websites run in Chrome. Other browsers are not covered yet.
- It checks what a person would see and do. It does not look inside your database, read your logs or confirm that an email arrived.
- It judges what is on the page, not how it looks: there is no pixel-by-pixel comparison of screenshots.
- A single run is limited to 10 minutes, which covers far longer journeys than most teams record.
One credit a run, however many checks are in it
A website run costs one credit: $1.75 on pay as you go, before tax. Every account starts with 50 free credits, enough to record your first journeys and watch them run on a schedule. No card, and no per-seat licence.