Traffic Router integration tests depend on an external Traffic Monitor #5992
Labels
improvement
The functionality exists but it could be improved in some way.
tech debt
rework due to choosing easy/limited solution
Traffic Router
related to Traffic Router
I'm submitting a ...
Traffic Control components affected ...
Current behavior:
In order to avoid Comcast/traffic_control#1665, Traffic Router integration tests require an actual Traffic Monitor in order to run:
trafficcontrol/traffic_router/core/src/test/java/com/comcast/cdn/traffic_control/traffic_router/core/dns/ZoneManagerTest.java
Line 69 in 5227543
trafficcontrol/traffic_router/core/src/test/java/com/comcast/cdn/traffic_control/traffic_router/core/loc/GeoTest.java
Line 47 in 5227543
trafficcontrol/traffic_router/core/src/test/java/com/comcast/cdn/traffic_control/traffic_router/core/router/StatelessTrafficRouterTest.java
Line 48 in 5227543
trafficcontrol/traffic_router/core/src/test/java/com/comcast/cdn/traffic_control/traffic_router/core/util/AbstractResourceWatcherTest.java
Line 61 in 5227543
New behavior:
The TR integration tests should use a mock Traffic Monitor server and mock Traffic Ops server like the external tests use:
trafficcontrol/traffic_router/core/src/test/java/com/comcast/cdn/traffic_control/traffic_router/core/external/ExternalTestSuite.java
Lines 106 to 107 in 5227543
Minimal reproduction of the problem with instructions:
traffic_router/core/src/test/conf/traffic_monitor.properties
if it existsThe text was updated successfully, but these errors were encountered: