iDarms Agent — Onboarding & First Launch Acceptance Tests¶
Test series: IDA-ONB-01 to IDA-ONB-03
Objective: Validate that the first-time launch sequence (notification permission, splash, onboarding, and entry to Login) behaves correctly and that the app does not repeat onboarding on subsequent launches.
Execution ownership¶
Recommended owners: Field Agent / iDarms Agent app users
Prerequisites: A clean device or a freshly reinstalled build of the app, with OS-level notification permissions reset to "not asked" / default.
Execution control
Use approved UAT devices only. Reset app data (uninstall/reinstall or clear app storage) between first-launch test passes so the sequence can be observed from a clean state.
Feature overview¶
On first launch, the app runs through: (1) a notification permission request, (2) a splash screen, (3) an onboarding screen, and (4) the Login screen. There is no self-registration path — agent credentials are always issued by the back office.
Coverage summary¶
| Test ID | Scenario | Priority |
|---|---|---|
| IDA-ONB-01 | Splash and onboarding screens | Medium |
| IDA-ONB-02 | Notification permission prompt | Medium |
| IDA-ONB-03 | First-launch sequence and re-launch behavior | High |
IDA-ONB-01 — Splash and onboarding screens¶
Feature overview¶
After the notification prompt is resolved, the app shows a splash screen followed by an onboarding screen before reaching Login.
Preconditions
- A clean install of the app.
| Field | Value |
|---|---|
| Priority | Medium |
| Test action | Launch the app for the first time and observe the splash and onboarding screens. |
| Expected result | Splash screen displays briefly, followed by an onboarding screen, then the Login screen. |
| Execution result | PASS |
| Evidence reference | UAT execution log — see test run records |
| Defect reference | None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Splash display | 1. Launch the app on a clean install. | The splash screen renders correctly and transitions automatically. | PASS |
Confirm branding and no visual glitches. |
| Onboarding content | 1. Observe the onboarding screen after splash. | Onboarding content is legible and any navigation controls (Next/Skip) work. | PASS |
|
| Continue to Login | 1. Complete or skip onboarding. | The app lands on the Login screen. | PASS |
No "Create Account" option should be present. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-ONB-02 — Notification permission prompt¶
Feature overview¶
On first launch, the OS-level notification permission dialog is triggered before the splash/onboarding sequence.
Preconditions
- Notification permission not previously granted or denied on the test device.
| Field | Value |
|---|---|
| Priority | Medium |
| Test action | Launch the app for the first time and respond to the notification permission prompt with Allow and, on a separate clean install, with Deny. |
| Expected result | The app proceeds to splash/onboarding/login regardless of the permission choice; denied permission does not block app usage. |
| Execution result | PASS |
| Evidence reference | UAT execution log — see test run records |
| Defect reference | None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Allow notifications | 1. Launch the app on a clean install. 2. Tap Allow on the OS prompt. |
The app proceeds normally to the splash screen. | PASS |
|
| Deny notifications | 1. Launch the app on a clean install. 2. Tap Deny/Don't Allow on the OS prompt. |
The app still proceeds to the splash screen; core functionality is not blocked. | PASS |
Confirm notifications can later be re-enabled via §4.7/More > Notification. |
| Prompt not repeated | 1. Force-close and relaunch the app after responding once. | The OS permission prompt does not appear again on subsequent launches. | PASS |
Standard OS behavior. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-ONB-03 — First-launch sequence and re-launch behavior¶
Feature overview¶
The full first-launch sequence (notification prompt → splash → onboarding → login) should only occur once; subsequent launches should go straight to Login (or the Dashboard, if a session is active).
Preconditions
- A clean install for the first-launch pass; the same install after completing the app once for the re-launch pass.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Complete the first-launch sequence, then close and reopen the app. |
| Expected result | Onboarding is not shown again; the app opens directly to Login or Dashboard depending on session state. |
| Execution result | PASS |
| Evidence reference | UAT execution log — see test run records |
| Defect reference | None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Re-launch without login | 1. Complete onboarding without logging in. 2. Close and reopen the app. |
The app opens directly to Login, skipping splash/onboarding repetition (splash screen itself may still show briefly on every launch). | PASS |
Confirm whether onboarding specifically, not splash, is a one-time screen. |
| Re-launch after login | 1. Log in successfully. 2. Close and reopen the app. |
The app opens to the Dashboard if the session is still valid (see IDA-AUTH-06). | PASS |
|
| Reinstall resets sequence | 1. Uninstall and reinstall the app. | The full first-launch sequence, including the notification prompt, occurs again. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.