[Resolved] Able to use Windows Server Name in Testcase?
I have built a Soap TestSuite that utilizes Windows Server Names for the endpoint URL (e.g. https://banshee1/rdeskt/20107/Proxy.svc, where "banshee1" is a valid windows server name). The TestSuite executes fine with a valid Soap return in SoapUI Pro, however, when placing it on our insite appliance to run, it continuously generates a "51" error: unable to resolve IP address. We are attempting to run these tests against specific physical servers that are behind a load balancer, therefore the need to address them directly.
The Testcase has a valid Host Header to provide the Web in the test.
As background I am attempting to avoid using a physical IP address as our servers occasionally change IPs which would make more work for us to maintain. I could have a DNS created strictly for the purpose of this testing, but when I discovered that the Windows Server Name would work in SoapUI Pro while testing, I was hoping we could avoid this extra work (we have many of these to build).
Are insite appliances not capable if resolving an address like SoapUI Pro does? I am running SoapUI Pro version 4.5.0 and our appliances have version 1.5.001 on them.
The Testcase has a valid Host Header to provide the Web in the test.
As background I am attempting to avoid using a physical IP address as our servers occasionally change IPs which would make more work for us to maintain. I could have a DNS created strictly for the purpose of this testing, but when I discovered that the Windows Server Name would work in SoapUI Pro while testing, I was hoping we could avoid this extra work (we have many of these to build).
Are insite appliances not capable if resolving an address like SoapUI Pro does? I am running SoapUI Pro version 4.5.0 and our appliances have version 1.5.001 on them.
