running same tests on a different server/environment

You have to change the service endpoint with a project property.
I have this in my project :
${#Project#endPointModeles_V1}
instead of a harcoded value generated by soapui

And i have add a project custom propertu
endPointModeles_V1=http://localhost:8080/scribe-web/ws/Modeles_v1_0

So this is the default endpoint.
Let say that i want to run them against http://SERVERB:8080/scribe-web/ws/Modeles_v1_0
I have to call the runner (maven plugin or whatever) with a endPointModeles_V1=ttp://SERVERB:8080/scribe-web/ws/Modeles_v1_0

This value will override the default value.

If the ovverid sytem doesnt work, make it work with a groovy script :

def modelesV1=context.expand('${#Project#endPointModeles_V1}');

def modelesV1=context.expand('${#Project#endPointModeles_V1}');
///Modeles_v1_0_SOAP
if( modelesV1 != null ) {
   log.info "Definition of enpoint service for ModelesV1 :"+modelesV1;
   project.interfaces["Modeles_v1_0_SOAP"].definition = modelesV1;
  }

look at the centralized endpoint example on this page - http://www.soapui.org/Functional-Testin ... rties.html

dmllc wrote:
look at the centralized endpoint example on this page - http://www.soapui.org/Functional-Testin ... rties.html

Tried this, but I still see

2011-01-31 08:17:28,988 INFO  [SchemaUtils] Loading schema types from [https://serverA/WebServices/SVPSWebService/CardComponent/CardInformation.asmx?WSDL]

in the soap-ui.log, where "serverA" is the endpoint that I coded my tests against and not what I passed with the -P. Which only leads to more questions.
Using the above technique, when I am running from the command line, is there any difference between using -PServiceEndoint=my.host and -hmy.host ? I suspect the answer is: no.
What exactly is "Loading schema types"? What will happen to my tests if this server is not reachable? I tried manually editing the -project.xml to something that does not exist, and the tests still appear to run fine.

TIA for any insight.

Yes and enpoint and a host is different.
But your dont need to precise for each server IF the difference between your endpoints SA & SB are juste ths host.

Example:
Endpoint for server A: htt://-HOSTA/stuf
Endpoint for server A: htt://-HOSTB-/stuf
But imagine that the endoint for server B was htt://-HOSTB-/superStufKebab
if you just precise the host for serverB, soapui will change in your default enpoint only the host.
Wich will lead to errors , endpoint not found.

"What exactly is "Loading schema types"?"
A wsdl import a A.XSD file wich imports B.xsd files etc.
So soapui in order to do his stuff (like schema compliance) will load not only your wsdl but those files too.

Try to put your wsdl in cache, so normally he will not at least try to download the wsdl (it speeds up the test but you have to update the cache
each time the wsdl change)
See the soapui Preferences.

mlenosgrande wrote:

Yes and enpoint and a host is different. But your dont need to precise for each server IF the difference between your endpoints SA & SB are juste ths host. Example: Endpoint for server A: htt://-HOSTA/stuf Endpoint for server A: htt://-HOSTB-/stuf But imagine that the endoint for server B was htt://-HOSTB-/superStufKebab if you just precise the host for serverB, soapui will change in your default enpoint only the host. Wich will lead to errors , endpoint not found.

All that makes sense. Thank You.

mlenosgrande wrote:

"What exactly is "Loading schema types"?" A wsdl import a A.XSD file wich imports B.xsd files etc. So soapui in order to do his stuff (like schema compliance) will load not only your wsdl but those files too. Try to put your wsdl in cache, so normally he will not at least try to download the wsdl (it speeds up the test but you have to update the cache each time the wsdl change) See the soapui Preferences.

I got the cache on, but that makes no difference when I am running my tests from the command line, right? Especially in a CI environment, where each test run starts from a completely fresh directory? So my original question still stands:

SiKing wrote:
All the actual tests ran against serverB, however, what if serverA is now completely offline? How do I get _everything_ in my suite to point to serverB?

have you done what i have told above without editing manally your file.
With that, you can precide unknow host and see errors.

mlenosgrande wrote:
have you done what i have told above without editing manally your file.

Yes I have. Your instruction are essentially the same as the tutorial that dmllc (also above) pointed me to. The problem still remains, the SopaUI grabs the schema from the original location. But the endpoint changes to whatever my variable points to.

mlenosgrande wrote:
With that, you can precide unknow host and see errors.

I don't know what that means.

Do the tests run if ServerA is offline? Try stopping your webserver.

I don't think soapUI is actually accessing ServerA to download anything. It is simply stating the URL where the schema info was originally downloaded from. The actual info is stored in cache, in your project file.

You could also try editing the soapUI project.xml and search for all instances of ServerA. Replace with ServerB, or even some non existent IP address. See if the tests still run successfully.

Unhandled wrote:
Do the tests run if ServerA is offline? Try stopping your webserver.

Yes. I even went so far as to edit this part of the -project.xml to some nonsense, and it still ran.

Unhandled wrote:
I don't think soapUI is actually accessing ServerA to download anything. It is simply stating the URL where the schema info was originally downloaded from. The actual info is stored in cache, in your project file.

I was was quite sure that I turned the caching off.

Unhandled wrote:
You could also try editing the soapUI project.xml and search for all instances of ServerA. Replace with ServerB, or even some non existent IP address. See if the tests still run successfully.

Did it, and it ran. I was just curious why is it telling me information that is essentially bogus and useless.

I finally found my answer ... in case anyone is reading this.
I followed the procedure suggested by dmllc above. But I also had to Update Definition (F5) for each of my WSDLs, and modify the centralized endpoint there as well.