Project Property manipulation
Hi Admin We use web based tool for doing daily smoke testing of our web services. The web based tool is also used by developers to kick off tests manually by selecting 2-3 choices. One of the ch...
Forum Discussion
I just want to share what i know the other way for running the tests on multiple environments. Below may more or less to what you are doing.
For each service interface level, using the endpoint url value as a property instead of server, port. And this property is put in a property file. For each environment, will maintain separate property file.
For eg:
Using ${#Project#ENDPOINT_URL} at service interface.
soapui.properties
ENDPOINT_URL=http://myhost:myport/service1
And in the load script, will load the properties from the above file, file name is read as System.getProperty('soapui.property') and pass argument -Dsoapui.property=<filename> to testrunner.
Server name, port are an example, you may use as many number of properties as needed.
For each service interface level, using the endpoint url value as a property instead of server, port. And this property is put in a property file. For each environment, will maintain separate property file.
For eg:
Using ${#Project#ENDPOINT_URL} at service interface.
soapui.properties
ENDPOINT_URL=http://myhost:myport/service1
And in the load script, will load the properties from the above file, file name is read as System.getProperty('soapui.property') and pass argument -Dsoapui.property=<filename> to testrunner.
Server name, port are an example, you may use as many number of properties as needed.