Fix test failures

Author: ali-ince

src/v1/internal/routing-util.js

@@ -50,7 +50,7 @@ export default class RoutingUtil {
       if (error.code === PROCEDURE_NOT_FOUND_CODE) {
         // throw when getServers procedure not found because this is clearly a configuration issue
         throw newError(
-          `Server at ${routerAddress} can't perform routing. Make sure you are connecting to a causal cluster`,
+          `Server at ${routerAddress.asHostPort()} can't perform routing. Make sure you are connecting to a causal cluster`,
           SERVICE_UNAVAILABLE);
       } else {
         // return nothing when failed to connect because code higher in the callstack is still able to retry with a

test/internal/connection-providers.test.js

@@ -957,6 +957,9 @@ describe('LoadBalancer', () => {
         'server02:7687': updatedRoutingTable
       }
     );
+    // override default use of seed router
+    loadBalancer._useSeedRouter = false;
+
     const usedRouterArrays = [];
     setupLoadBalancerToRememberRouters(loadBalancer, usedRouterArrays);
 
@@ -1057,6 +1060,8 @@ describe('LoadBalancer', () => {
         'server02:7687': routingTable2
       }
     );
+    // override default use of seed router
+    loadBalancer._useSeedRouter = false;
 
     loadBalancer.acquireConnection(READ).then(connection1 => {
       expect(connection1.address).toEqual(serverC);