Parameterized WSDL Location

Hi,

you can use property-expansion syntax in the WSDL location property, for example if you create a project-level property named "WsdlHost" you could then use it in your WSDL urls with "${#Project#WsdlHost}/path/to/my.wsdl"

Is this what you had in mind?

regards,

/Ole
eivware.com

The problem is that when I add the WSDL's initially, they are added with the details of the machine that I referred the WSDL from.  For different developers this will not be the same and every developer should be able to run the same suite from their own machine using their own unique locations.  LocalHost works but it still refers to the machine name in the schema references etc. so I was looking to parameterize all of that so that I replace it once and it reflects everywhere where a location is required.

Hi again!

so my above suggested solution should work!?

1) Create a project-level property named "WsdlHost" and set its value to the initial host you want to import from
2) Add a WSDL to your project and specify ${#Project#WsdlHost}/path/to/wsdl as the WSDL endpoint
3) Change the value of the WsdlHost property as desired on different machines

Or am I misunderstanding?

regards!

/Ole
eviware.com

Being quite new to soapUI it seems like you already support this scenario in that when you execute the test suite you can dynamically specify the host against which to run it.  This also applies to the command line testrunner.bat invocation through using the /h parameter.  This allows me to run the same tests against any host, correct?

Hi,

If I understand you correctly you are asking about the possibility of dinamicaly changing endpoints against which you run the tests?

When opening Interface under ServiceEndpoints tab you can specify a number of different endpoints which than you can change on TestRequest level of execution. However since a TestCase can contain TestRequests tied to different interfaces you can't do the same on TestCase (nor TestSuite) level.

Hope this helps you.
Regards, Dragica

Hi,

you can also use properties in your endpoints to easily change the target server for a number of requests, ie define a property at the Project level (for example "TestHost") and then use it in your endpoints with for example "${#Project#TestHost}/path/to/service". You can then override the TestHost value from the command-line using the -P option, ie -PTestHost=http://some.otherhost.com

The -h option is primarily viable when you are using only one target host in all your requests (since it will change all hosts to the specified value)

Hope this helps!

regards,

/Ole
eviware.com

Hi,
this was exactly what I was looking for anyway!

Thanks
/Abe