Automated mobile app testingOn real phones, without writing code
Upload your Android or iPhone build and tap through it once on a real phone, saying what should be true on each screen. BitAssure walks the same journey again as often as you like and tells you in your own words what still holds.
No card needed.
- Home shows "Hello, Thabo"
- The balance reads $4,120.00
- Top up is enabled
- Notifications are onFound switched off, 1:04 into the video
A real phone, the build you uploaded, installed fresh.
What a customer sees on their phone, said in your words
Tap through your app the way a customer would. On each screen, tap anything and write what should be true about it. That sentence is the check.
Home shows "Hello, Thabo"
Signing in and onboarding
Record it once, permissions and pop-ups included. Every other journey can start from it, so it is never recorded twice.
Confirm is enabled
Forms on a phone
Typing, dropdowns, date pickers, switches, scrolling to something further down: each is a step, walked the way a thumb would.
The balance reads $4,120.00
Figures and messages
A balance, a total, a confirmation. Exactly what you expect, or containing the part you care about.
Notifications are on
Switches and states
On or off, enabled or disabled, shown or gone, at the moment in the journey it should be, not only at the end.
Real phones, your real build
Not an imitation of your app: the build you ship, installed on a real phone, tapped the way a person taps it.
Your build, on a real phone
Upload your .apk or .ipa. BitAssure reads which app it is from the build itself and installs it fresh for every run.
Recorded by tapping
The phone is on your screen. Tap through the app, and add checks as you go. Nothing is written as code, and nothing is added to your app.
On a schedule, or from CI
Hourly, daily, every weekday or weekly on every plan, or from your pipeline with an API key when a new build is ready.
A video of every run
The phone's screen is recorded, with every check marked at the moment it was judged, so a failure is watched rather than reproduced.
Permissions answered
Permission requests are accepted automatically, or left for the journey to answer, so "allow notifications" never stops a run by surprise.
A report anyone can read
Pass or fail, screen by screen, in the sentences your team wrote, as a page or a PDF.
What it does not do, so you can plan around it
- Android is the most proven. iPhone apps run on real iPhones too, but that is newer, and an iPhone's calendar-style date picker is not handled yet.
- It checks what a person would see and do. It does not look inside your database, read your logs or confirm that a push notification arrived.
- A phone run is limited to 15 minutes, and stops earlier if the account's credits run out, saying so.
- An app that talks to a server only reachable inside your network cannot be tested yet: the connector carries websites so far.
- It judges what is on the screen, not how it looks: there is no pixel-by-pixel comparison of screenshots.
Charged by the minute the phone is yours
A phone costs one credit a minute, counted from when your app is ready, not while the phone is being prepared. $1.75 a credit on pay as you go, before tax. Every account starts with 50 free credits.