FireSafeX Test Report

New flow, local stack: end-to-end browser suite

Passed 68/68

68 of 68 browser tests passed.

Run started
Run time
14 min 03 s
Screenshots
190
Browser
Chromium, 1400 × 900
  1. 17/7Flow 1: Set up a new customer
  2. 25/5Flow 2: Courses: one shared library, customised per organization
  3. 36/6Flow 3: Assess employees
  4. 47/7Flow 4: A certificate's life: issued, valid until, expired, renewed
  5. 55/5Flow 5: Employee sign-in on the Quest: select your name
  6. 64/4Flow 6: Employee sign-in on the web or mobile app: name + employee ID
  7. 76/6Flow 7: Kits: pairing, activation and tracking
  8. 86/6Flow 8: Firmware update
  9. 95/5Flow 9: A device has a problem
  10. 109/9Flow 10: AI usage: limits, tracking, export
  11. R6/6Roles
  12. P2/2Phone width (390 px)

Who did each step

No role mismatches: every screenshot was taken as a role of its steps, or as a role noted below. 190 of 190 screenshots record who was signed in (120 read from the page header, 42 from the sign-in where a dialog covered the header, 28 simulators, public and signed-out pages).

Steps whose test also signs in as another role, by design:

  • 1.3 Activates each Quest and kit together: Quest simulator Mako activates the Quest with the kit code on the headset itself.
  • 3.8 Follows up or reschedules: Quest simulator The rescheduled employee retakes on the Quest, so the follow-up shows the new result.
  • 4.5 Retakes and passes: Org admin The org admin checks the coverage on Overview after the renewal.
  • 6.6 Join a live quiz: Org admin The org admin hosts the live quiz the employee joins.
  • 10.7 Raises the limit: Org admin The organization's own admin sees the warning gone after the super admin raised the limit.

Each screenshot is checked against the lanes of the steps its test covers: Super admin, Org admin, Org admin · Manager (or the firmware simulator, their mobile app), Employee (or the Quest), the simulators. Signed-out and public pages count for anyone.

Browser suite68/68This run, end to end in Chromium
Server tests174API unit and integration tests, as of 19 Nov 2026
App tests497Flutter admin panel and employee app tests, as of 19 Nov 2026

Server and app tests run separately; e2e.sh does not run them. Counts as of 19 Nov 2026.

Not covered

  • Live voice on the QuestThe typed text path stands in for speech when the employee asks the AI expert.
  • The no-Gemini-key pathThe server's offline stub answer is not exercised.
  • The real Quest app and real BluetoothThe Quest headset and the companion app with its device are played by the simulators.

Flow 1

Set up a new customer

From a new organization to employees training. The customer never activates anything.

  1. 1.1
    Super admin (Mako)Creates the organizationPlatform › Organizations

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  2. 1.2
    Super admin (Mako)Works through the setup checklistInvites the org admin, chooses modules, languages and courses

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  3. 1.3
    Super admin (Mako)Activates each Quest and kit togetherWith the kit code, before shipping. The Quest is now set to this organization

    Step for: Super admin (Mako)Screenshots as Super admin, Quest simulatorRoles matchAlso as Quest simulator, by design

    Passed
    1.3super admin pairs a device and activates Quest and kit with the kit code
    Passed15 s4 screenshots

    Signed in as Local Super Admin · Super adminQuest simulator

    Also as Quest simulator Mako activates the Quest with the kit code on the headset itself.

  4. 1.4
    Super admin (Mako)Ships the kits

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  5. 1.5
    Org adminAccepts the invite and signs inLands on the organization overview

    Step for: Org adminScreenshots as Org adminRoles match

    Passed
  6. 1.6
    Org adminAdds employeesEach gets an employee ID

    Step for: Org adminScreenshots as Org adminRoles match

    Passed

    Tested with 1.5–1.6, shown under step 1.5.

  7. 1.7
    EmployeeStarts trainingOn the Quest by selecting their name; on the web or mobile app with name + employee ID

    Step for: EmployeeScreenshots as Employee, Quest simulatorRoles match

    Passed
  8. 1.8
    Super admin (Mako)Overview shows Ready
    Org adminOverview shows Ready

    Step for: Super admin (Mako) + Org adminScreenshots as Super admin, Org adminRoles match

    Passed

Flow 2

Courses: one shared library, customised per organization

Every course holds its chapters and two assessments: a Theory assessment and an Immersive assessment

  1. 2.1
    Super admin (Mako)Creates a course in Course libraryChapters, Theory assessment, Immersive assessment, translations

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  2. 2.2
    Super admin (Mako)Publishes itEvery library course goes to all organizations by default

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed

    Tested with 2.1–2.2, shown under step 2.1.

  3. 2.3
    Org admin · ManagerFinds it in CoursesMarked by where it came fromLibrary

    Step for: Org admin · ManagerScreenshots as Org adminRoles match

    Passed
  4. 2.4
    Org admin · ManagerUses it as is, or customises itA course changes only when someone changes it inside that organization. That makes the organization's own copyCustomised

    Step for: Org admin · ManagerScreenshots as Org adminRoles match

    Passed

    Tested with 2.3–2.5, shown under step 2.3.

  5. 2.5
    Org admin · ManagerAdds the organization's own coursesEach also has both assessmentsOwn

    Step for: Org admin · ManagerScreenshots as Org adminRoles match

    Passed

    Tested with 2.3–2.5, shown under step 2.3.

  6. 2.6
    Org admin · ManagerPublishes and schedulesFlow 3

    Step for: Org admin · ManagerScreenshots as Org admin, EmployeeRoles match

    Passed
  7. 2.7
    EmployeeSees all three kinds together

    Step for: EmployeeScreenshots as Org admin, EmployeeRoles match

    Passed

    Tested with 2.6–2.7, shown under step 2.6.

  8. 2.8
    Super admin (Mako)Updates the library course later

    Step for: Super admin (Mako)Screenshots as Super admin, Org adminRoles match

    Passed
    2.8–2.9a library update reaches unedited organizations; the edited one sees "Newer library version"
    Passed29 s5 screenshots

    Signed in as Local Super Admin · Super adminNora Admin · Org adminHugo Admin · Org admin

    One test covers steps 2.8 and 2.9.

  9. 2.9
    Org admin · ManagerNot edited: gets the update automaticallyEdited: keeps its own copy, and sees "Newer library version" to review if it wants

    Step for: Org admin · ManagerScreenshots as Super admin, Org adminRoles match

    Passed

    Tested with 2.8–2.9, shown under step 2.8.

Flow 3

Assess employees

One connected loop from scheduling to follow-up, covering both assessments of a course

  1. 3.1
    Org admin · ManagerOpens a courseLibrary, customised or own

    Step for: Org admin · ManagerScreenshots as ManagerRoles match

    Passed
  2. 3.2
    Org admin · ManagerPublish & schedule in one stepWho, when, deadline

    Step for: Org admin · ManagerScreenshots as ManagerRoles match

    Passed

    Tested with 3.1–3.2, shown under step 3.1.

  3. 3.3
    EmployeeSees it assigned, with its deadline

    Step for: EmployeeScreenshots as EmployeeRoles match

    Passed
  4. 3.4
    EmployeeTakes the Theory assessmentQuestions and a score

    Step for: EmployeeScreenshots as EmployeeRoles match

    Passed

    Tested with 3.3–3.4, shown under step 3.3.

  5. 3.5
    EmployeeTakes the Immersive assessmentOn the Quest with the FireSafeX device; scored per skill

    Step for: EmployeeScreenshots as Quest simulatorRoles match

    Passed
  6. 3.6
    EmployeeGets the result and certificateFlow 4

    Step for: EmployeeScreenshots as EmployeeRoles match

    Passed
  7. 3.7
    Org admin · ManagerOpens the schedule's resultsPassed, failed, overdue, per person and per assessment

    Step for: Org admin · ManagerScreenshots as ManagerRoles match

    Passed
  8. 3.8
    Org admin · ManagerFollows up or reschedules

    Step for: Org admin · ManagerScreenshots as Manager, Quest simulatorRoles matchAlso as Quest simulator, by design

    Passed
    3.8follow-up: overdue and failed employees are rescheduled
    Passed11 s5 screenshots

    Signed in as Milo Manager · ManagerQuest simulator

    Also as Quest simulator The rescheduled employee retakes on the Quest, so the follow-up shows the new result.

Flow 4

A certificate's life: issued, valid until, expired, renewed

Certificates expire 1 year after they are issued

  1. 4.1
    EmployeePasses and receives the certificateIt shows the issue date and "Valid until"IssuedValid

    Step for: EmployeeScreenshots as EmployeeRoles match

    Passed
  2. 4.2
    Org admin · ManagerSees each employee's certificate statusOn People and on Overview: how many are covered right now

    Step for: Org admin · ManagerScreenshots as Org adminRoles match

    Passed
  3. 4.3
    Org admin · ManagerWarned before it lapsesThe employee is listed for renewalExpiring soon
    EmployeeSees "Expires on…" in the appExpiring soon

    Step for: Org admin · Manager + EmployeeScreenshots as Employee, Org adminRoles match

    Passed

    Tested with 4.2/4.3/4.6, shown under step 4.2.

  4. 4.4
    Org admin · ManagerSchedules the renewalThe same course again

    Step for: Org admin · ManagerScreenshots as Org adminRoles match

    Passed
  5. 4.5
    EmployeeRetakes and passesA new certificate with a new "Valid until"Renewed

    Step for: EmployeeScreenshots as Employee, Org adminRoles matchAlso as Org admin, by design

    Passed
    4.5the employee retakes and passes: a new certificate, the old one is Renewed
    Passed15 s3 screenshots

    Signed in as Employee app: Chen Wei · NWL-000005Public page (Employee app: Chen Wei · NWL-000005)Nora Admin · Org admin

    Also as Org admin The org admin checks the coverage on Overview after the renewal.

  6. 4.6
    EmployeeIf not renewed in timeThe certificate and its public verification page show it as expiredExpired
    Org admin · ManagerEmployee counts as not coveredExpired

    Step for: Employee + Org admin · ManagerScreenshots as Employee, Org adminRoles match

    Passed

    Tested with 4.2/4.3/4.6, shown under step 4.2.

Flow 5

Employee sign-in on the Quest: select your name

Nothing is typed on the headset: no organization code, no name, no employee ID, no PIN

  1. 5.1
    Quest headsetAlready set to its organizationDone by Mako before shipping

    Step for: Quest headsetScreenshots as Quest simulatorRoles match

    Passed
  2. 5.2
    Quest headsetLists all the organization's employees

    Step for: Quest headsetScreenshots as Quest simulatorRoles match

    Passed

    Tested with 5.1–5.3, shown under step 5.1.

  3. 5.3
    EmployeeSelects their own nameThat is the whole sign-in

    Step for: EmployeeScreenshots as Quest simulatorRoles match

    Passed

    Tested with 5.1–5.3, shown under step 5.1.

  4. 5.4
    EmployeeChooses Theory or Immersive

    Step for: EmployeeScreenshots as Quest simulatorRoles match

    Passed
  5. 5.5
    Quest headsetTheoryLessons and the Theory assessment

    Step for: Quest headsetScreenshots as Quest simulatorRoles match

    Passed

    Tested with 5.4–5.6/5.8–5.9, shown under step 5.4.

  6. 5.6
    Quest headsetImmersiveHands-on mixed-reality training and the Immersive assessment
    FireSafeX deviceDrives the simulationPin, aim and squeeze go to the Quest; the device vibrates back

    Step for: Quest headset + FireSafeX deviceScreenshots as Quest simulatorRoles match

    Passed

    Tested with 5.4–5.6/5.8–5.9, shown under step 5.4.

  7. 5.7
    EmployeeCan ask the AI expert by voice

    Step for: EmployeeScreenshots as Quest simulatorRoles match

    Passed
  8. 5.8
    Quest headsetSaves the result under that employee

    Step for: Quest headsetScreenshots as Quest simulatorRoles match

    Passed

    Tested with 5.4–5.6/5.8–5.9, shown under step 5.4.

  9. 5.9
    EmployeeNext person selects their own name

    Step for: EmployeeScreenshots as Quest simulatorRoles match

    Passed

    Tested with 5.4–5.6/5.8–5.9, shown under step 5.4.

Additional checks

Tests in this flow that check something next to the numbered steps.

Flow 6

Employee sign-in on the web or mobile app: name + employee ID

Where an employee checks courses, statuses and certificates. No PIN or other secret

  1. 6.1
    EmployeeOpens the employee appNo organization code or link needed

    Step for: EmployeeScreenshots as EmployeeRoles match

    Passed
  2. 6.2
    EmployeeTypes their name and employee IDThat is the whole sign-in; the employee ID finds the organization

    Step for: EmployeeScreenshots as EmployeeRoles match

    Passed

    Tested with 6.1–6.2, shown under step 6.1.

  3. 6.3
    Web / mobile appMy trainingCourses assigned, with status and deadline

    Step for: Web / mobile appScreenshots as EmployeeRoles match

    Passed
  4. 6.4
    Web / mobile appResultsTheory and Immersive assessment scores

    Step for: Web / mobile appScreenshots as EmployeeRoles match

    Passed

    Tested with 6.3–6.5, shown under step 6.3.

  5. 6.5
    Web / mobile appCertificatesIssued on, valid until, expired; download

    Step for: Web / mobile appScreenshots as EmployeeRoles match

    Passed

    Tested with 6.3–6.5, shown under step 6.3.

  6. 6.6
    Web / mobile appJoin a live quiz

    Step for: Web / mobile appScreenshots as Org admin, EmployeeRoles matchAlso as Org admin, by design

    Passed
  7. 6.7
    EmployeeSigns outClears their identity and cached data from the device

    Step for: EmployeeScreenshots as EmployeeRoles match

    Passed

Flow 7

Kits: pairing, activation and tracking

One FireSafeX device is paired to exactly one Quest. All tracking and status changes happen in the super admin panel

  1. 7.1
    Super admin (Mako)Pairs the device to its QuestExclusive: one to one

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  2. 7.2
    Super admin (Mako)Activates the Quest and the kit togetherWith the kit code, before shipping

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  3. 7.3
    Kit (Quest + device)Arrives ready to useThe customer activates nothing

    Step for: Kit (Quest + device)Screenshots as Super adminRoles match

    Passed

    Tested with 7.2–7.5, shown under step 7.2.

  4. 7.4
    Kit (Quest + device)Shared across the organizationEach session is saved under the employee who selected their name

    Step for: Kit (Quest + device)Screenshots as Super adminRoles match

    Passed

    Tested with 7.2–7.5, shown under step 7.2.

  5. 7.5
    Super admin (Mako)Re-pairs when a part is replacedOnly a super admin can

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed

    Tested with 7.2–7.5, shown under step 7.2.

  6. 7.6
    Super admin (Mako)Tracks every kit and deviceIn Platform › Hardware › Kits & devices

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  7. 7.7
    Super admin (Mako)Changes a kit's or device's status thereStatuses are changed only in the super admin panel

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  8. 7.8
    Org admin · ManagerSees the organization's kits in DevicesFirmware version and issues; cannot change a status

    Step for: Org admin · ManagerScreenshots as Manager, Org adminRoles match

    Passed

Flow 8

Firmware update

Both sides can see which devices are on the latest version and which are not

  1. 8.1
    Super admin (Mako)Uploads and validates a releasePlatform › Hardware › Firmware

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  2. 8.2
    Super admin (Mako)Publishes to one organization or severalNone pre-selected

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  3. 8.3
    Org admin · ManagerSees which devices are outdatedUpdate available

    Step for: Org admin · ManagerScreenshots as ManagerRoles match

    Passed
  4. 8.4
    Org admin · ManagerOpens the FireSafeX mobile app next to the devicesSigned in with their own staff account

    Step for: Org admin · ManagerScreenshots as Firmware simulatorRoles match

    Passed
  5. 8.5
    Companion app + deviceConnects to one device over Bluetooth and installs the updateSeveral devices: one by one

    Step for: Companion app + deviceScreenshots as Firmware simulatorRoles match

    Passed

    Tested with 8.4–8.6, shown under step 8.4.

  6. 8.6
    Companion app + deviceDevice reports its new version

    Step for: Companion app + deviceScreenshots as Firmware simulatorRoles match

    Passed

    Tested with 8.4–8.6, shown under step 8.4.

  7. 8.7
    Super admin (Mako)Sees how many are on the latestWith the list of devices that are not
    Org admin · ManagerDevice shows as currentUp to date

    Step for: Super admin (Mako) + Org admin · ManagerScreenshots as Manager, Super adminRoles match

    Passed

Flow 9

A device has a problem

A ticket both sides can follow

  1. 9.1
    Org admin · ManagerDevices › kit › Report an issueDescribes what is wrong

    Step for: Org admin · ManagerScreenshots as ManagerRoles match

    Passed
  2. 9.2
    Super admin (Mako)Ticket arrives in Hardware › Support ticketsOpen

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  3. 9.3
    Super admin (Mako)Takes the ticketNotes are visible to the organizationIn progress

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed

    Tested with 9.2–9.3, shown under step 9.2.

  4. 9.4
    Super admin (Mako)Decides the fixRemote helpRepairReplace
    Kit statusSuper admin changes the kit's statusIn Platform › Hardware

    Step for: Super admin (Mako) + Kit statusScreenshots as Super adminRoles match

    Passed
  5. 9.5
    Super admin (Mako)Closes the ticketResolved

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed

    Tested with 9.4–9.5, shown under step 9.4.

  6. 9.6
    Org admin · ManagerFollows it in Devices › IssuesStatus and notes at every step

    Step for: Org admin · ManagerScreenshots as ManagerRoles match

    Passed

Flow 10

AI usage: limits, tracking, export

Each organization has a monthly allowance of AI tokens and voice characters

  1. 10.1
    Super admin (Mako)Sets the organization's monthly limitsPlatform › AI usage

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed
  2. 10.2
    Quest trainer + translationUsage adds upVoice trainer in the Quest, course translation, speech

    Step for: Quest trainer + translationScreenshots as Super admin, Org adminRoles match

    Passed
  3. 10.3
    Org admin · ManagerOverview cardUsed this month against the limit

    Step for: Org admin · ManagerScreenshots as Org admin, ManagerRoles match

    Passed
  4. 10.4
    Org admin · ManagerAI usage pageDaily trend and every requestExport CSV

    Step for: Org admin · ManagerScreenshots as Org admin, ManagerRoles match

    Passed

    Tested with 10.3–10.5, shown under step 10.3.

    Tested with 10.3–10.5, shown under step 10.3.

  5. 10.5
    Super admin (Mako)Warned as an organization nears its limit
    Org admin · ManagerWarned as the limit nears

    Step for: Super admin (Mako) + Org admin · ManagerScreenshots as Super admin, Org admin, ManagerRoles match

    Passed

    Tested with 10.3–10.5, shown under step 10.3.

    Tested with 10.3–10.5, shown under step 10.3.

  6. 10.6
    Quest trainer + translationAt the limit, the AI stops

    Step for: Quest trainer + translationScreenshots as Org admin, Super admin, Manager, Quest simulatorRoles match

    Passed
  7. 10.7
    Super admin (Mako)Raises the limitRecorded with who and when

    Step for: Super admin (Mako)Screenshots as Super admin, Org adminRoles matchAlso as Org admin, by design

    Passed

    Tested with 10.1/10.7, shown under step 10.1.

  8. 10.8
    Super admin (Mako)Exports usage for all organizations or oneExport CSV

    Step for: Super admin (Mako)Screenshots as Super adminRoles match

    Passed

Additional checks

Tests in this flow that check something next to the numbered steps.

Checks

Roles

Who may do what: managers cannot remove users, org admins cannot act on another org admin, and platform pages redirect everyone but the super admin.

Checks

Phone width (390 px)

The employee app and a staff page on a 390 px wide phone screen.

17 fixes

Fixed along the way

Problems the suite found while it was being written, now fixed in the code it tests.

Results and certificates

  • Immersive results from the Quest were refused: the course title was read from an empty field.
  • A Theory result said Failed on one screen and Passed on another.
  • Staff pages showed stale results until a reload.
  • The public certificate page could show another certificate's details, and redirected staff on reload.

Sign-in and accessibility

  • Employee sign-in failed when autocorrect changed the typed name. Autocorrect is off and the server tolerates spacing and character variants.
  • Staff and employee menus were missing for screen readers.
  • The employee app's selected menu label was invisible.

Forms and messages

  • The organization image was required; it is now optional.
  • The invite form showed one server error at a time.
  • Firmware file slots were ambiguous.
  • A new message waited behind an old one: a refused pairing still said "Kit created."
  • The course page's own-copy notice was replaced by "Saved."
  • A live quiz could not be created when the organization's language differed from the course text language.

AI usage

  • Seeded AI usage was rewritten by the usage rebuild job.
  • Reaching the AI limit only showed the 80% warning.

Seed data

  • The seed had no free device to pair, and could stop halfway, leaving no kits.
  • The seed printed the wrong super admin password.
Open image