Signing in to the UAT Tester

The UAT Tester is where your agency runs its acceptance testing before a Smart Squad release goes live — a generated test cycle for the features you actually have enabled, on the platforms you actually deploy, finishing with an electronic sign-off.

Open the UAT Tester

You will need an account — see below.

Before you sign in

UAT Tester accounts are separate from your Smart Squad login. Your usual officer credentials will not work here, and there is no self-service sign-up. Accounts are created for you.

Who has which role

CoordinatorCreates and manages your agency’s test cycles, invites testers, and is the person to ask for access.

TesterWorks through the assigned tests and records the result of each one.

SignatoryReviews the completed cycle and signs it off on the agency’s behalf.

Getting an account

If your agency is already set up Ask your agency’s UAT coordinator to add you. They can create your account and set a temporary password for you.
If this is your agency’s first cycle Contact Faction Four support. We create your agency and your first coordinator; from there your coordinator adds everyone else.
Sign in Open the UAT Tester and sign in with the email address and temporary password you were given.
Set your own password You will be asked to change the temporary password the first time you sign in. Choose something only you know — the temporary one was visible to whoever created your account.
Start testing Your home screen lists the test runs assigned to you. Choose one and select Start — there is nothing to configure first.

Forgotten your password? There is currently no “forgot password” email. Ask your agency coordinator to set you a new temporary password, and change it when you next sign in.

If you are the coordinator, contact Faction Four support and we will reset it.

Using it on a phone

The tester is built to be used on a phone, because you will usually have the device under test in your other hand. Everything works in a mobile browser — there is no app to install.

Recording a result

Each test asks for one decision. A few rules are enforced, so that a completed cycle means something:

PassNothing further needed.

FailDescribe what you did and what happened, and attach a photo. Both are required.

SkipGive a reason. Skipped tests are visible on the sign-off certificate.

BlockedUse when something needed isn’t available — a second device, a printer, a supervisor. Give a reason and come back to it.

Use test data, never live records. Photos and screenshots attached to a failed test are stored with the result. Do not capture real people, real plates or real occurrence details.