Frequently asked questions
What BitAssure does, what it needs from you, and where its limits are. If something you need is not here, ask us directly.
Getting started
Do I need to know how to code?
No. You walk through your own app in a browser and say what each screen should show. Nothing you do is written as code, and there is nothing to install.
How long does setting up take?
A first checklist on a short journey takes a few minutes. The time is mostly spent clicking through your app once, which you would be doing anyway.
Does BitAssure need access to my source code?
No. It uses your application the way a customer does, through the browser or the app itself. It never reads your repository and never needs to be installed alongside your code.
Can I test a site that is behind a login?
Yes. Make signing in part of the journey, and every later run signs in the same way before it checks anything.
How it works
What exactly is a check?
A statement about one thing on one screen: that a button works, that a total reads a particular figure, that a message appears. Each one is judged on its own, so one failure never hides the others behind it.
What is a journey?
A named flow through your app, such as signing in or paying. It is a container: you move through that flow once, adding your checks as you go, and they all live under that one name. A login journey, for instance, just holds the checks that say login works and the right things are on screen.
Will my checks break every time the design changes?
A check is attached to the thing on screen rather than to its position, so moving something or restyling it does not break the check. Removing it or renaming what it is does, which is usually what you want to hear about.
What happens when a check fails?
The report names the check that failed, says what it found instead, and points at the moment in the run recording where it happened, so you can watch it rather than trying to reproduce it.
Coverage and limits
Which browsers and devices do you run on?
Websites run on real Chrome. Mobile apps run on real Android devices. iOS support is built but has not yet been proven on a real device, so we would rather you did not rely on it yet.
Can I run checks automatically on a schedule?
Not yet. Runs are started by you, or from your own CI using an API key. Scheduled and recurring runs are the next thing we are building.
Can BitAssure test things it cannot see?
No, and this is a real limit worth knowing. It checks what a person would see and do. It does not inspect your database, read your logs, or verify that an email actually arrived.
Is this a replacement for engineers writing tests?
No. It covers the paths a customer takes through your product, which is the part most often left untested. Unit and integration tests written by engineers cover different ground, and the two sit happily side by side.
Accounts and billing
What counts as one run?
One checklist executed against one target, however many checks are on it. Fifty checks on one screen is one run, not fifty.
Am I charged for a run that finds a failure?
Yes, it did its job. You are not charged for a run that fails because of a fault on our side.
How many people can I add?
As many as you like. Billing is based on the runs you make, not on the number of seats, because charging per seat discourages exactly the people you want writing checks.
What happens to my data if I leave?
You can delete anything at any time. When an account is closed, its data is removed within 30 days. The detail is in the Privacy Policy.
Still deciding?
A free account is enough to build a real checklist and see a real report before you commit to anything.