Picking the right tester setup

Zantiq by Nomina testers start with a Basic identity, then you add capabilities only when a flow needs them. That keeps simple QA affordable while still supporting more complex products.

Basic is the starting point. Your tester gets a realistic persona, an email inbox, saved credentials, screenshots, and QA reports. That covers basic signup, login, password reset, invite, and form-completion tests.

Phone Tester adds a dedicated phone number and inbound SMS capture. Use it when your flow requires phone verification, two-factor authentication, SMS invites, or approval codes.

Browser Tester adds a persistent browser profile on top of the Basic identity. The browser keeps cookies, sessions, and fingerprint consistency across test runs. This matters if your app or its auth providers run fingerprint checks, and it also helps when a re-run should start from known saved credentials or a remembered session.

Workspace Tester combines email, phone, persistent browser, and workspace-style account support. This is the right setup for invite flows, multi-user approval flows, admin/member workflows, and tests where the same tester needs to keep state across many sessions.

Managed Identity is the high-touch option for OAuth-heavy products, social login, payment flows, and manual approval paths. It is intentionally not fully automatic because those ecosystems often require review, verification, or customer-specific setup.

A few rules of thumb. If you're just testing basic signup: Basic. If you need SMS: add Phone. If you need cookies, sessions, or fingerprint consistency: add Browser. If you have invite or multi-user workflows: use Workspace. If you have OAuth, payments, or high-friction account creation: use Managed Identity.

You can add capabilities to a tester anytime. The new identity components get provisioned on top of what's already there, so the tester's history does not need to reset.