From 590a176100d8dbe097c6411961ed28270386f911 Mon Sep 17 00:00:00 2001 From: mcilwain Date: Wed, 8 Feb 2017 09:14:29 -0800 Subject: [PATCH] Remove local server restriction in unit tests config Unit tests still won't be able to fire up a local server for other reasons, but it is reasonable to at least allow URLs to be constructed from within tests so as to be able to make assertions about conditions that would allow connections to be made successfully. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=146917889 --- .../registry/config/files/nomulus-config-unittest.yaml | 6 ------ 1 file changed, 6 deletions(-) diff --git a/java/google/registry/config/files/nomulus-config-unittest.yaml b/java/google/registry/config/files/nomulus-config-unittest.yaml index 9a55fd1f2..dbd78efe0 100644 --- a/java/google/registry/config/files/nomulus-config-unittest.yaml +++ b/java/google/registry/config/files/nomulus-config-unittest.yaml @@ -1,12 +1,6 @@ # This is the configuration file used by unit tests. These values ARE NOT # SUITABLE for use in a real deployed environment. -appEngine: - # Tests can't fire up a full server, so make them error out if they try to. - toolsServiceUrl: - hostName: null - port: 0 - registryPolicy: registrarChangesNotificationEmailAddresses: - notification@test.example