d are performed carefully and methodically. But for operators who are just interested in getting their 5G radios deployed, some might suspect obvious amounts of overkill. For their sake, the following list highlights the tests that are most important for everyday deployments: End-to-end network frequency wander: Frequency wander tests are easy to set up and ex- ecute, SO it makes sense to perform them. The performance is rarely an issue with SyncE, but frequency testing may be necessary if, for example, you use it to detect a timing loop in the net- work. The other possible (troubleshooting) case is where every node in the chain appears to be faithfully reproducing the frequency signal, but the hardware is not doing what it claims (in ESMC values). See the following section "Field Testing." End-to-end network phase alignment: Getting your network in phase and keeping it there is really the goal of this whole book, SO it makes sense to measure phase alignment. Every oper- ator wants to perform these tests to see what the phase alignment is at the end of the timing dis- tribution network and what happens to it under various conditions and events. Holdover: It is vital to understand that when the PTP and SyncE (or both) signals are interrup- ted in the timing network, what happens to the clocks downstream? Typically, most operators test this by removing the timing signal(s) from the last clock in the chain and monitoring the phase alignment over time. It is also a good test to investigate the difference between holdover assisted by SyncE and oscillator holdover. Network rearrangements: This is testing the case when the T-GM for the timing chain fails and the network selects another source, or there is a network arrangement upstream of the last clock. Similar cases involve monitoring TE during events like control plane processor switchovers in those same network elements. Frequency clock (EEC/eEE) tests: The frequency tests executed most often would be wander noise generation, but even then, most engineers are not th