TR Ultimate Test Harness - Delivery Service of type HTTP is selected when performing a DNS Test.

[davidc0le]

This Bug Report affects these Traffic Control components:

• Traffic Router ( the TR testing infraturure, not the TR itself)

Current behavior:

When starting the Ultimate Test Harness without a specifically selected Delivery Service, the tool connects to Traffic Ops and selects a delivery service of type HTTP and uses it for both HTTP and DNS benchmarking.

Both HTTP and DNS code paths use function GetTrafficRouterDetails in main_test.go to get the TR specifics, including the DS. Per the following: https://github.com/apache/trafficcontrol/blob/c0b747c18799952a4db7566c5a0f5dd9a5989c95/traffic_router/ultimate-test-harness/main_test.go#L104 GetTrafficRouterDetails only will select a DS of type HTTP.

Expected behavior:

I think the harness should use a DS of type DNS for DNS benchmarking and of type HTTP for HTTP benchmarking.

Steps to reproduce:

Run the hardness in default mode ( DNS + HTTP benchmarking) with your Traffic Ops setup to have one or more HTTP delivery services and one or more DNS delivery services. The output will only list HTTP delivery services as being benchmarked.