In Phase 2, we are testing the extended multi-network and multi-unit coordination capabilities by integrating the Tower Base Stations, the Communications Controller, and their interactions with both radio and broadband paths. This phase adds the logic that manages repeater towers, RF repeaters, interoperability gateways, and routing across different communication paths while still using test harnesses in place of the full dispatch and user interfaces. As a result, we will be directly testing the following requirements from the original document: FR-2 creation and modification of talk groups and assignment of channels at the system level as reflected in how towers and controllers apply configuration updates, FR-3 automatic network switching in a more realistic environment that includes RF, LTE, WiFi, and P25 links with varying quality, FR-5 real time monitoring of units, groups, users, and relay towers with status such as online or offline state and channel usage, FR-6 support for multiple units and departments sharing information by joining the same communication group and exchanging messages in real time, FR-8 automatic switchover to backup communication paths when the primary path is degraded or fails, and FR-9 recording of call and alert events across towers and gateways for later investigation. We will also indirectly exercise FR-1 and FR-4, because normal PTT and emergency traffic will traverse this integrated network, but the primary focus will be on how the infrastructure routes, prioritizes, and monitors those flows. The tests in this phase will involve driving traffic through the Tower Base Stations and Communications Controller using multiple simulated radios and mobile app clients, inducing interference and failures on different links, verifying that status and usage information is correctly aggregated for monitoring, and confirming that routing and failover behavior match the expected group and channel configurations.
| Id | Test Case Objective | Test Case Description | Expected Results |
|---|---|---|---|
| P2-01 | Verify the configuration of the towers and controllers upon group and channel assignments (FR-2). | Through the test harness, assign several simulated endpoints (i.e. radios and apps) to one of two talk groups and assign appropriate channels. Move some, but not all, endpoints from one talk group to the other and update the channels as appropriate. | Controllers and towers shall update their configurations to reflect the changes as directed by the commands sent via the dispatch module. Two talk groups should exist with the expected participating endpoints; each with the expected channel. |
| P2-02 | Verify automatic network switching based on current availability and network stability. (FR-3, FR8) | Within a simulated or controlled network environment begin with a known number of endpoints, on each network type (RF, LTE, WiFi, P25); quality of each network should vary across test instances. The number of endpoints on each network should be a quantity where the network is not “stressed”. Gradually degrade the performance of a network type until its stability / bandwidth is affected. Multiple instances should be run with varying types of networks being degraded. | The controller should automatically switch the radios, sitting on the network(s) targeted by degradation, to an alternative network with more stability. Switched devices should distributed across the remaining networks based on real time network performance, ensuing one network type is not flooded and degraded. |
| P2-03 | Verify real time monitoring of units, talk groups, users, and relay towers’ statuses (FR-5) | The test harness shall have a known number of endpoints configured in the system. Endpoints should have varying states of connected and disconnected, utilize a mix of network types (LTE, WIFI, radio), and have varying known, signal conditions. | Values reported out by the real time monitoring system should be equivalent to the known values configured within the test harness. |
| P2-04 | Verify different organizations can join the same talk group (FR-6) | Multiple organizations should be configured within the testing environment, each with a varying number of devices connected across different network types. Each organization should join one of two talk groups. | When each device sends a communication, all devices within the talk group should receive the communication in real time, as established in NFR-4. Devices not in that talk group should not receive the communication. |
| P2-05 | Verify endpoints switch to a new network when the connected network fails. (FR-8) | Within the testing environment, connect several devices to each of the network types. Artificially invoke a network failure of on network type. This test case should be repeated for all network types. | All devices on the failed network should automatically switch to the remaining functional and/or backup networks. Abnormal conditions should be reported. |
| P2-06 | Confirm system logging. (FR-9, FR-1, FR4) | Within the test environment initiate several calls and alerts at known times from various radios | Confirm the logs reflect the appropriate time, channel, participating units, and users for each call and alert |
| P2-07 | Verify the emergency alerts preempt non-emergency communication. (FR-4) | With multiple devices connected to the system, across different network types, have one device transmit a non-emergency communication. During this transmission, trigger an emergency communication from a second device. | Confirm the emergency communication is prioritized above the non-emergency communication and that the command center and related units receive the emergency communication even across varying network types. |