Biometrics
Pass or fail a fingerprint, Face ID or PIN prompt yourself during a Live session — so you can test the login, payment and unlock flows that sit behind biometric authentication.
Many apps open with a biometric prompt — banking, payments, password managers, healthcare, enterprise sign-in. With no one physically holding the phone, those flows would be stuck. TestKase lets you answer the prompt yourself — approve it, reject it, or cancel — so you can drive what sits behind the lock.
Turn it on
Biometrics is a per-build setting, so you prepare it once:
- Upload your app (or pick one from My apps) — see Installing Apps.
- Open App settings (the ⚙ next to the build) and switch Biometric on.
- Wait for the build to show Ready — we prepare a copy of it for biometric testing, which takes about a minute the first time. Your uploaded file is left untouched.
Then start a session with that build. With the Biometric switch off, the app runs exactly as you uploaded it.
Biometrics works on Android and iPhone, on real devices and virtual ones (Android emulators and iOS simulators). The same switch and the same choices apply everywhere.
Answer the prompt
When the app asks for a fingerprint, Face ID or the device PIN, a Pass / Fail / Cancel choice appears. Pick the result and the app continues:
- Pass — the system reports a match. The app behaves exactly as it would after a real, successful scan.
- Fail — a mismatch, so you can test the retry prompt and the lock-out after too many tries.
- Cancel — the prompt is dismissed, so you can test the fallback to a PIN or to another sign-in method.
On Android the choice appears as a prompt in your TestKase session. On iPhone it appears as a sheet on the phone itself — tap Pass, Fail or Cancel on the streamed screen.
Covered prompts: fingerprint (Touch ID), Face ID, and the device passcode that apps fall back to.
A real result, not a real finger
No actual finger or face is scanned. The result is simulated through the operating system's own testing hooks, so your app's real authentication code runs and receives a genuine success or failure — the retry prompt, the lock-out, the PIN fallback all run for real. No biometric data leaves the device's secure hardware.
It does not test the physical sensor, enrollment, or anti-spoofing.
In automated tests
You can answer the same prompt from an Appium script, so biometric branches run in your suites. See Automate → Biometrics.
Good to know
- The prepared copy is made per settings combination and once — the ~1-minute wait is only when you change the switches, not every session.
- Uploaded iOS builds are re-signed to install on a managed device; the same caveats apply as for any installed
.ipa— see Installing Apps.
Installing Apps
Get your app onto a device — upload an .ipa or .apk (or a zipped simulator .app for a virtual iPhone), reuse it from My apps, or install a published app from the App Store or the Play Store.
Camera injection
Feed your app's camera a chosen still image — a QR code, barcode, ID or document — during a Live session instead of the live camera, so you can test scanning, KYC and document-capture flows.