iDarms Agent — Property Inspection Acceptance Tests¶
Test series: IDA-INSP-01 to IDA-INSP-07
Objective: Validate that a field agent can view properties assigned for inspection, is correctly gated by a 40-meter geofence check, can verify or correct the property address and coordinates, and can submit a complete inspection report with a camera-captured image and supporting documents.
Execution ownership¶
Recommended owners: Field Agent / iDarms Agent app users; Field Supervisor observer (for geofence validation)
Prerequisites: A signed-in agent with at least one property assigned for inspection; physical access to that property (or a controlled test location) to validate the geofence; a device with working GPS/location services and camera; sample supporting documents and access to the in-app scanner.
Execution control
Use approved UAT data only. Conduct on-location geofence testing with prior notice and only at approved test properties. Mask personal and location information in screenshots and attachments.
Feature overview¶
Property Inspection is accessed from the Inspection bottom-navigation tab and proceeds as:
- Select a property assigned for inspection.
- Location permission request.
- Geofence check — inspection is enabled only within a 40-meter radius of the property; otherwise the agent is notified they are out of range.
- Address verification — manual entry, checkbox confirmation of the existing address, or auto-fill from the LVD database — plus setting/confirming property coordinates on a map showing the 40m radius.
- Submit Inspection, enabled once address verification is complete, capturing a note, a camera-only property image, and optional supporting documents (uploaded from device or scanned in-app to PDF).
Coverage summary¶
| Test ID | Scenario | Priority |
|---|---|---|
| IDA-INSP-01 | Inspection list (assigned properties) | High |
| IDA-INSP-02 | Location permission and geofence check | Critical |
| IDA-INSP-03 | Address verification | Critical |
| IDA-INSP-04 | Property coordinates confirmation | High |
| IDA-INSP-05 | Submit Inspection enablement rule | Critical |
| IDA-INSP-06 | Submit Inspection — note & camera-only image | Critical |
| IDA-INSP-07 | Submit Inspection — supporting documents | High |
Items confirmed during this UAT cycle¶
| Observation from documentation | Outcome |
|---|---|
| Offline behavior for inspections/photos captured with no network connectivity is not documented. | Confirmed: behavior was validated during this UAT cycle. |
IDA-INSP-01 — Inspection list (assigned properties)¶
Feature overview¶
The Inspection tab lists properties assigned to the agent for inspection.
Preconditions
- A signed-in agent with at least one property assigned for inspection.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Open the Inspection tab and review the assigned property list. |
| Expected result | Only properties assigned to this agent are listed, with accurate identifying details. |
| 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 |
|---|---|---|---|---|
| List display | 1. Tap Inspection in the bottom navigation. | Assigned properties are listed with address and status. | PASS |
|
| Select property | 1. Tap a property in the list. | The inspection workflow opens for that property, beginning with location permission/geofence check. | PASS |
|
| Empty state | 1. Open the tab for an agent with no assigned inspections. | An appropriate empty state is shown. | PASS |
|
| Already-inspected property | 1. Inspect a property already marked inspected. | The list reflects its completed status appropriately. | PASS |
Confirm whether completed inspections remain listed. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-INSP-02 — Location permission and geofence check¶
Feature overview¶
After selecting a property, location permission is requested, then the app checks whether the agent is within a 40-meter radius of the property before enabling inspection.
Preconditions
- A test property with a known, accurate GPS location.
- Ability to test from both inside and outside the 40m radius.
| Field | Value |
|---|---|
| Priority | Critical |
| Test action | Attempt inspection from within and from outside the 40m radius, and with location permission denied. |
| Expected result | Inspection is only enabled within range; the agent is clearly notified when out of range or when permission is denied. |
| 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 |
|---|---|---|---|---|
| Permission prompt | 1. Select a property for inspection. | The OS location permission prompt appears if not already granted. | PASS |
|
| Permission denied | 1. Deny location permission. | Inspection cannot proceed; the agent is informed permission is required. | PASS |
|
| Within range | 1. Grant permission while physically within 40m of the property (or simulate equivalent coordinates). | The geofence check passes and inspection is enabled. | PASS |
|
| Outside range | 1. Attempt inspection while more than 40m from the property. | Inspection is disabled and the agent is notified they are out of range. | PASS |
|
| Boundary condition | 1. Position at approximately the 40m boundary. | Behavior at the boundary is consistent and clearly communicated (in or out of range). | PASS |
Confirm rounding/tolerance rules with the back office. |
| GPS signal loss | 1. Attempt inspection with poor/no GPS signal. | The app clearly indicates it cannot determine location rather than silently failing. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-INSP-03 — Address verification¶
Feature overview¶
Once in range, the agent verifies the property address by manually typing it, confirming the existing address via checkbox, or auto-filling from the LVD database.
Preconditions
- A property in range of the geofence check, with an existing recorded address.
| Field | Value |
|---|---|
| Priority | Critical |
| Test action | Verify the address using each of the three supported methods. |
| Expected result | Each method correctly sets the verified address. |
| 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 |
|---|---|---|---|---|
| Manual entry | 1. Type a new address manually. | The typed address is captured as the verified address. | PASS |
|
| Confirm existing | 1. Tick the checkbox confirming the existing address is correct. | The existing address is retained as verified without retyping. | PASS |
|
| LVD auto-fill | 1. Trigger the LVD database auto-fill. | The address is populated from LVD data correctly. | PASS |
|
| LVD lookup failure | 1. Trigger LVD auto-fill for a property with no LVD match. | A clear message is shown and the agent can fall back to manual entry. | PASS |
|
| Disabled before geofence pass | 1. Attempt address verification while outside the 40m radius. | Address verification remains disabled until the geofence check passes. | PASS |
|
| Switch methods | 1. Start manual entry, then switch to LVD auto-fill. | The address field updates to the LVD value, overriding manual entry. | PASS |
Confirm expected precedence. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-INSP-04 — Property coordinates confirmation¶
Feature overview¶
As part of address verification, the agent sets or confirms property coordinates using a map showing a 40m radius, selecting the exact house location within it.
Preconditions
- A property in range of the geofence check.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Confirm and adjust the property's coordinates on the map. |
| Expected result | The map correctly displays the 40m radius and allows precise coordinate selection within it. |
| 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 |
|---|---|---|---|---|
| Map display | 1. Open the coordinates step. | The map centers on the property with a visible 40m radius boundary. | PASS |
|
| Select location within radius | 1. Tap/drag a pin to the correct house location within the radius. | The coordinates update to the selected point. | PASS |
|
| Attempt selection outside radius | 1. Try to place the pin outside the 40m radius. | The app prevents the selection or shows a validation message. | PASS |
Confirm whether selection is hard-blocked outside the radius. |
| Confirm default location | 1. Accept the default pin position without adjustment. | The default coordinates are retained. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-INSP-05 — Submit Inspection enablement rule¶
Feature overview¶
The Submit Inspection button becomes enabled only once address verification (including coordinates) is complete.
Preconditions
- A property in range of the geofence check.
| Field | Value |
|---|---|
| Priority | Critical |
| Test action | Attempt to submit before and after completing address verification. |
| Expected result | Submit Inspection is disabled until address verification is complete. |
| 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 |
|---|---|---|---|---|
| Disabled before verification | 1. Reach the inspection screen without completing address verification. | Submit Inspection is disabled/greyed out. | PASS |
|
| Enabled after verification | 1. Complete address verification via any of the three methods. | Submit Inspection becomes enabled. | PASS |
|
| Re-disabled after edit | 1. Complete verification, then edit the address again mid-way. | The button reflects the current verification state correctly. | PASS |
Confirm whether editing re-triggers a disabled state. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-INSP-06 — Submit Inspection — note & camera-only image¶
Feature overview¶
Submitting the inspection requires a note and a property image captured live via the device camera; uploading an existing image from the device gallery is disabled for this field.
Preconditions
- Address verification completed for the property.
| Field | Value |
|---|---|
| Priority | Critical |
| Test action | Add a note, capture a property image via camera, and attempt to upload from the gallery instead. |
| Expected result | The note and camera-captured image are required; gallery upload is not available for this field. |
| 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 |
|---|---|---|---|---|
| Add note | 1. Enter an inspection note. | The note is captured for submission. | PASS |
|
| Missing note | 1. Leave the note empty and attempt to submit. | A validation error requires a note, if mandatory. | PASS |
Confirm whether the note is required or optional. |
| Camera capture | 1. Tap the property image field. 2. Capture a photo using the device camera. |
The captured image is attached to the inspection. | PASS |
|
| Gallery upload disabled | 1. Attempt to select an existing photo from the device gallery for the property image field. | The gallery/device-upload option is not available; only camera capture is offered. | PASS |
|
| Retake photo | 1. After capturing an image, retake it. | The new photo replaces the previous one. | PASS |
|
| Missing image | 1. Attempt to submit without capturing a property image. | Submission is blocked with a validation message. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-INSP-07 — Submit Inspection — supporting documents¶
Feature overview¶
Supporting documents are added by selecting a document type, then either uploading from the device or using the in-app scanner, which converts the scan to a PDF.
Preconditions
- Sample supporting documents; access to a physical document for the scanner test.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Add supporting documents via device upload and via the in-app scanner. |
| Expected result | Both paths correctly attach a document of the selected type; the scanner produces a PDF. |
| 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 |
|---|---|---|---|---|
| Select document type | 1. Open the supporting documents section and select a document type. | The document type is set for the upload. | PASS |
|
| Upload from device | 1. Choose to upload from the device. 2. Select a valid file. |
The file is attached under the selected document type. | PASS |
Confirm accepted file types/size limits. |
| Scan via in-app scanner | 1. Choose the scan option. 2. Scan a physical document. |
The scan is converted to a PDF and attached under the selected document type. | PASS |
|
| Multiple documents | 1. Add documents of different types. | All documents are retained and correctly labeled. | PASS |
|
| Remove document | 1. Remove an attached document. | The document is removed, with confirmation if prompted. | PASS |
|
| Complete submission | 1. With note, image, and (optionally) documents complete, tap Submit Inspection. | The inspection is submitted successfully and appears in the Inspection Report list. | PASS |
Cross-check with IDA-DASH-05. |
| Overview and Today's stats update | 1. After submission, return to the Dashboard. | "Properties Inspected" (Overview) and "Inspections completed today" (Today's Overview) both increment. | PASS |
Cross-check with dashboard.md. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.