Unit Test Protocol (Prime Order Portal)
Acceptance checklist for Prime Order Portal — “does this app work?”. Business-level UAT lives in UAT & ISP Processes.
How to use
Run against staging with real coverage and product data.
Mark each row pass / fail; note the address and product used.
Agree with the customer which rows block go-live.
Checklist
# | Check | Pass when | Blocks go-live? |
|---|---|---|---|
1 | Address autocomplete | City → ZIP → street → house number resolves a real address | Yes |
2 | Available result | A covered FTTH address returns available with correct products | Yes |
3 | Product-class differentiation | FTTH / VDSL / HFC / radio return the expected class per address | Yes |
4 | Pre-order / planning result | An in-build address returns pre-orderable or in planning | Yes |
5 | Expected timeframe & texts | Configured status text / timeframe shows (e.g. “FTTH by Q2/2026”) | Recommended |
6 | Negative result | An uncovered address returns not available | Yes |
7 | Alternatives | Alternatives appear on a negative / mismatched result | Recommended |
8 | Waitlist | Sign-up stores an entry; it appears in export | Recommended |
9 | Order → contract | Completed order creates a contract in NMS Prime | Yes |
10 | Provisioning | Approved order triggers provisioning (DOCSIS / FTTH / DSL) | Yes |
11 | Online payment | Signature + payment verification complete for a test order | If in scope |
12 | Multi-address API | Batch query returns per-address status | If in scope |
13 | Waitlist export API | Export returns registered entries | If in scope |
14 | White-label UI | Theme matches brand; referral link tracked | Recommended |
Sign-off
Role | Name | Date | Result |
|---|---|---|---|
Shop admin |
|
|
|
Care / ops |
|
|
|
Delivery |
|
|
|