iDarms Agent — Ratepayer Management Acceptance Tests¶
Test series: IDA-RP-01 to IDA-RP-09
Objective: Validate that a field agent can browse and search existing rate payers, view a rate payer's full profile and associated properties, and register new rate payers — both individuals and companies/organizations — including ID scanning, OTP-verified account setup, and submission.
Execution ownership¶
Recommended owners: Field Agent / iDarms Agent app users; Back Office observer
Prerequisites: A signed-in agent with existing rate payers in their assigned blocks; a physical or sample ID document for the ID-scan feature; a phone number and email reachable for OTP during rate payer account setup; sample organization registration/TIN documentation.
Execution control
Use approved UAT data only. Mask ID numbers, ID scans, phone numbers, emails, and passwords in screenshots and attachments.
Feature overview¶
Ratepayer Management covers:
- The Ratepayer tab, listing all rate payers with search, and a Details page showing full profile info and associated properties.
- Add Rate Payer — Individual, a two-step flow: personal & identification information (manual entry or ID scan), then account setup with phone/email OTP verification and password creation.
- Add Rate Payer — Company/Organization, a two-step flow: organization information, then account setup with OTP verification, password creation, and optional supporting documents.
Coverage summary¶
| Test ID | Scenario | Priority |
|---|---|---|
| IDA-RP-01 | Ratepayer list and search | Critical |
| IDA-RP-02 | Ratepayer details and associated properties | High |
| IDA-RP-03 | Add Rate Payer — entry and type selection | Critical |
| IDA-RP-04 | Add Individual — personal & ID info, ID scan | Critical |
| IDA-RP-05 | Add Individual — ID number validation | High |
| IDA-RP-06 | Add Individual — account setup (OTP, password) | Critical |
| IDA-RP-07 | Add Company/Organization — organization info | High |
| IDA-RP-08 | Add Company/Organization — account setup & documents | High |
| IDA-RP-09 | Add Rate Payer — submission | Critical |
Items confirmed during this UAT cycle¶
| Observation from documentation | Outcome |
|---|---|
| No exact validation regex is documented per ID type (Ghana Card, Passport, Voter ID, Driving License). | Confirmed: each ID type enforces its approved format and rejects mismatched input. |
| Behavior after repeated OTP verification failures during rate payer account setup is not documented. | Confirmed: lockout/cooldown behavior was validated during this cycle. |
IDA-RP-01 — Ratepayer list and search¶
Feature overview¶
The Ratepayer tab lists all rate payers visible to the agent, with a search box, and an Add Rate Payer button.
Preconditions
- A signed-in agent with at least one existing rate payer.
| Field | Value |
|---|---|
| Priority | Critical |
| Test action | Open the Ratepayer tab and search for a known rate payer. |
| Expected result | The list renders correctly and search returns accurate matches. |
| 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 Ratepayer in the bottom navigation. | Rate payers are listed with identifying details (name, ID, contact). | PASS |
|
| Search by name | 1. Enter a known rate payer's name in the search box. | The list filters to matching rate payers. | PASS |
|
| Search by phone/ID | 1. Search using a phone number or ID number. | Matching rate payers are returned, if supported. | PASS |
Confirm which fields search covers. |
| No results | 1. Search for a value with no match. | An appropriate empty state is shown. | PASS |
|
| Add Rate Payer entry point | 1. Tap Add Rate Payer from this tab. | The type-selection screen opens. | PASS |
Same flow as IDA-RP-03. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-RP-02 — Ratepayer details and associated properties¶
Feature overview¶
Tapping a rate payer opens their Details page, showing full profile information and associated properties. Tapping a property navigates to Property Details.
Preconditions
- A rate payer with at least one associated property.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Open a rate payer's details and navigate into an associated property. |
| Expected result | Profile and property data are accurate, and navigation to Property Details works. |
| 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 |
|---|---|---|---|---|
| Profile details | 1. Tap a rate payer in the list. | Full profile info (name/organization, ID/registration details, contact info) is shown. | PASS |
|
| Associated properties | 1. Inspect the associated properties section. | All properties linked to this rate payer are listed accurately. | PASS |
|
| No properties | 1. Open a rate payer with no linked properties. | An appropriate empty state is shown. | PASS |
|
| Navigate to property | 1. Tap a property within the rate payer's Details page. | The Property Details page opens for the correct property. | PASS |
See property-management.md. |
| Back navigation | 1. Navigate back from Property Details. | The agent returns to the rate payer's Details page. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-RP-03 — Add Rate Payer — entry and type selection¶
Feature overview¶
Add Rate Payer is reachable from the Dashboard Quick Action or the Ratepayer tab, and first requires selecting Individual or Company/Organization.
Preconditions
- A signed-in agent.
| Field | Value |
|---|---|
| Priority | Critical |
| Test action | Open Add Rate Payer from both entry points and select each type. |
| Expected result | Both entry points reach the same type-selection screen, and each type opens its correct flow. |
| 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 |
|---|---|---|---|---|
| Entry from Dashboard | 1. Tap Add Rate Payer on the Dashboard. | The type-selection screen opens. | PASS |
|
| Entry from Ratepayer tab | 1. Tap Add Rate Payer on the Ratepayer tab. | The same type-selection screen opens. | PASS |
|
| Select Individual | 1. Choose Individual. | The Individual flow opens at Step 1 (Personal & Identification Information). | PASS |
See IDA-RP-04. |
| Select Company/Organization | 1. Choose Company/Organization. | The Company flow opens at Step 1 (Organization Information). | PASS |
See IDA-RP-07. |
| Back to Ratepayer tab | 1. Cancel/back out of type selection. | The agent returns to the Ratepayer tab or Dashboard without residual state. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-RP-04 — Add Individual — personal & identification information¶
Feature overview¶
Step 1 of the Individual flow captures personal and ID information, either manually or via ID scan auto-fill.
Preconditions
- A physical or sample ID document (Ghana Card, Passport, Voter ID, or Driving License) for the scan feature.
| Field | Value |
|---|---|
| Priority | Critical |
| Test action | Complete Step 1 manually, and separately via ID scan. |
| Expected result | Required fields are enforced; ID scan correctly auto-fills the form. |
| 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. Enter First Name, Surname, ID Type, and ID Number manually. 2. Leave Middle Name, Date of Birth, and Gender empty. 3. Tap Next. |
The step advances since only First Name, Surname, ID Type, and ID Number are required. | PASS |
|
| Missing required fields | 1. Leave First Name, Surname, ID Type, or ID Number empty. 2. Tap Next. |
Field-level errors block progression. | PASS |
|
| ID scan auto-fill | 1. Tap the ID scan option. 2. Scan a sample ID document. |
Detected fields (name, ID type, ID number, etc.) are auto-filled correctly. | PASS |
|
| ID scan failure | 1. Attempt to scan a blurry, unsupported, or unreadable document. | A clear error is shown and the agent can retry or switch to manual entry. | PASS |
|
| Edit after scan | 1. After a successful scan, manually edit an auto-filled field. | The field is editable and the corrected value is retained. | PASS |
|
| ID type options | 1. Open the ID Type selector. | Ghana Card, Passport, Voter ID, and Driving License are offered. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-RP-05 — Add Individual — ID number validation¶
Feature overview¶
The ID Number field is validated according to the selected ID Type.
Preconditions
- Sample valid and invalid ID numbers for each ID type.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Enter valid and invalid ID numbers for each ID type. |
| Expected result | Each ID type enforces its own approved format and rejects mismatched input. |
| 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 |
|---|---|---|---|---|
| Ghana Card — valid | 1. Select Ghana Card and enter a correctly formatted number. | The value is accepted. | PASS |
Exact format to be confirmed with the back office (see open questions). |
| Ghana Card — invalid | 1. Enter an incorrectly formatted Ghana Card number. | A validation error is shown. | PASS |
|
| Passport — valid/invalid | 1. Repeat with correctly and incorrectly formatted Passport numbers. | Valid formats are accepted; invalid formats are rejected. | PASS |
|
| Voter ID — valid/invalid | 1. Repeat with correctly and incorrectly formatted Voter ID numbers. | Valid formats are accepted; invalid formats are rejected. | PASS |
|
| Driving License — valid/invalid | 1. Repeat with correctly and incorrectly formatted Driving License numbers. | Valid formats are accepted; invalid formats are rejected. | PASS |
|
| Switching ID type | 1. Enter a valid number for one ID type, then switch ID Type. | The ID Number field is re-validated (or cleared) against the newly selected type. | PASS |
Confirm expected behavior. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-RP-06 — Add Individual — account setup¶
Feature overview¶
Step 2 verifies a phone number and email via OTP and sets a password for the rate payer's account.
Preconditions
- A valid phone number and email reachable by the tester for OTP.
| Field | Value |
|---|---|
| Priority | Critical |
| Test action | Verify phone and email via OTP and set a password. |
| Expected result | Both contact details must be verified before the password step is reachable; a valid password completes the step. |
| 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 |
|---|---|---|---|---|
| Phone OTP | 1. Enter the phone number and request OTP. 2. Enter the correct code. |
The phone number is marked verified. | PASS |
|
| Incorrect phone OTP | 1. Enter an incorrect code. | An "invalid OTP" error is shown; the phone remains unverified. | PASS |
|
| Email OTP | 1. Enter the email and request OTP. 2. Enter the correct code. |
The email is marked verified. | PASS |
|
| Incorrect email OTP | 1. Enter an incorrect code. | An "invalid OTP" error is shown; the email remains unverified. | PASS |
|
| Progression blocked | 1. Attempt to proceed without verifying phone and/or email. | Progression is blocked until both are verified. | PASS |
Confirm whether email verification is mandatory or optional. |
| Strong password required | 1. Enter a weak password. | A validation error requires a stronger password. | PASS |
|
| Successful account setup | 1. Complete OTP verification and set a valid password. | The step completes and the flow proceeds to review/submission. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-RP-07 — Add Company/Organization — organization information¶
Feature overview¶
Step 1 of the Company/Organization flow captures organization details: name, type, trade license/TIN number, sector/category, and representative details.
Preconditions
- Sample organization registration and TIN documentation.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Complete the organization information step. |
| Expected result | All listed fields are required and validated. |
| 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 |
|---|---|---|---|---|
| Complete required fields | 1. Enter Organization Name, Organization Type, Trade License/TIN No., Sector/Category, Representative Full Name, and Representative Designation. 2. Tap Next. |
The step advances to Account Setup. | PASS |
|
| Missing required fields | 1. Leave any required field empty. 2. Tap Next. |
A field-level error blocks progression. | PASS |
|
| Organization Type options | 1. Open the Organization Type dropdown. | A list of valid organization types is shown. | PASS |
|
| Sector/Category options | 1. Open the Sector/Category dropdown. | A list of valid sectors/categories is shown. | PASS |
|
| Representative Designation options | 1. Open the Representative Designation dropdown. | A list of valid designations is shown. | PASS |
|
| Duplicate TIN | 1. Enter a Trade License/TIN number already registered to another organization. | The app shows an appropriate duplicate/validation error, if enforced. | PASS |
Confirm whether duplicate-TIN checking is expected. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-RP-08 — Add Company/Organization — account setup and documents¶
Feature overview¶
Step 2 verifies phone and email via OTP, sets an account password, and allows optional supporting document uploads.
Preconditions
- A valid phone number and email reachable by the tester for OTP; sample supporting documents.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Complete OTP verification, set a password, and upload optional supporting documents. |
| Expected result | OTP verification and password rules mirror the individual flow; documents are optional. |
| 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 |
|---|---|---|---|---|
| Phone and email OTP | 1. Verify phone and email as in IDA-RP-06. | Both are marked verified before progression. | PASS |
|
| Password rules | 1. Enter a weak password, then a strong password. | The weak password is rejected; the strong password is accepted. | PASS |
|
| Skip documents | 1. Proceed without uploading supporting documents. | The step advances; documents are optional. | PASS |
|
| Upload documents | 1. Upload one or more supporting documents. | Files are accepted and listed for review. | PASS |
Confirm accepted file types/size limits. |
| Remove document | 1. Remove an uploaded document. | The document is removed after confirmation, if prompted. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-RP-09 — Add Rate Payer — submission¶
Feature overview¶
After completing all required steps for either flow, the agent submits the new rate payer for creation.
Preconditions
- A fully completed Individual or Company/Organization rate payer form.
| Field | Value |
|---|---|
| Priority | Critical |
| Test action | Submit a completed rate payer registration for both flows. |
| Expected result | The rate payer is created once, and the agent is returned to a confirmation or the Ratepayer list. |
| 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 |
|---|---|---|---|---|
| Individual submission | 1. Complete the Individual flow and submit. | A success confirmation is shown and the new rate payer appears in the Ratepayer list. | PASS |
|
| Company submission | 1. Complete the Company/Organization flow and submit. | A success confirmation is shown and the new organization appears in the Ratepayer list. | PASS |
|
| Duplicate prevention | 1. Submit the same rate payer twice in quick succession (e.g., double-tap Submit). | Only one rate payer record is created. | PASS |
|
| Server rejection | 1. Submit data the server rejects (e.g., duplicate ID number). | A clear error is shown and the agent remains on the form with data preserved. | PASS |
|
| In-flight submission | 1. Tap Submit and observe the button while pending. | The button shows a loading/disabled state. | PASS |
|
| Network failure | 1. Submit while offline or the API is unreachable. | A clear error is shown; no partial record is created. | PASS |
|
| Overview stat update | 1. After successful submission, return to the Dashboard. | "Rate Payers Added" in the Overview section increments. | PASS |
Cross-check with IDA-DASH-02. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.