Rate Payer Portal & Ratepayer Apps UAT¶
Integrated Digital Addressing and Revenue Management System Phase 3 – Segment 1
This controlled documentation supports business-led User Acceptance Testing for the Rate Payer Portal (web) and Ratepayer Apps (iOS and Android). Both applications serve ratepayers and share common test coverage areas, but are maintained as separate test suites with independent navigation.
Document status
Version: 1.0 Status: Ready for UAT execution Classification: Controlled UAT Copy Credentials: Not included
Applications covered¶
Rate Payer Portal (Web)¶
Web-based portal for ratepayers to manage identity, properties, bills, payments, receipts, claims, and account settings.
| Area | Test series | Cases |
|---|---|---|
| Ratepayer Portal | RPP |
16 |
| Ratepayer Portal Authentication | RPP-AUTH |
16 |
| Subtotal | 32 |
Ratepayer Apps (iOS & Android)¶
Native mobile apps mirroring portal functionality with app-specific navigation, biometric login, onboarding, and receipt sharing.
| Area | Test series | Cases |
|---|---|---|
| Ratepayer Apps | RPA |
16 |
| Subtotal | 16 |
Combined total: 48 cases¶
How to use this site¶
- Review the UAT scope, roles, entry criteria, environment, and evidence rules.
- Navigate to the application section (Portal or Apps) relevant to your test cycle.
- Assign acceptance-test pages to the appropriate business testers.
- Execute each test against the recorded release/build and controlled data.
- Record result, actual outcome, evidence, and defect reference.
- Retest fixes and execute affected regression cases.
- Complete the final acceptance decision and sign-off.
Result values¶
| Result | Meaning |
|---|---|
PASS |
Expected business outcome achieved with acceptable evidence. |
FAIL |
Actual outcome materially differs from the expected result. |
BLOCKED |
Execution cannot continue because a prerequisite or dependency is unavailable. |
NOT RUN |
Case has not yet been executed. |
N/A |
Case is not applicable and includes an approved justification. |