Unit Test Protocol (Prime Detect)
Unit Test Protocol (Prime Detect)
App-level checks: does Prime Detect work for this tenant? Cross-app ISP journeys live under UAT & ISP Processes.
# | Check | Pass when |
|---|---|---|
1 | Module available | Detect enabled; authorized users open the Detect Dashboard |
2 | Trouble board | Impaired hosts/services appear (or empty board with known-healthy plant) |
3 | Mute | Muting a test problem changes its visibility / muted state |
4 | Topography | Pilot net/cluster MAP shows positioned net elements |
5 | ERD | ERD opens for the same net with parent/child relations |
6 | Icinga list | Host or service list opens from Detect |
7 | State history | History opens for a host with recent state changes |
8 | Customer context | With provisioning: modems/customers visible in geo context |
9 | Ticket hook | With Ticket: impairment can be linked/raised as work |
10 | Permissions | Users without Detect rights cannot open dashboard / maps |
Record date, tester, environment, and defects. Keep this page short — expand only with checks that repeatedly catch real failures.