Forum Discussion
kralston
12 years agoOccasional Contributor
I am trying a similar thing in a Transfer test step.
In a previous version of SoapUI I did not have to include a namespace declaration. Since upgrading to 4.6.4 my generic Transfer XPaths are all failing without the namespace declaration.
With multiple test environments I was reading in the endpoints, etc. from an external config file and loading them into Properties. Inside the config file I could specify the run environment and all worked nicely.
I am looking for a way to use one or more properties to build the namespace declaration on the fly so that my tests will support multiple environments.
In a previous version of SoapUI I did not have to include a namespace declaration. Since upgrading to 4.6.4 my generic Transfer XPaths are all failing without the namespace declaration.
With multiple test environments I was reading in the endpoints, etc. from an external config file and loading them into Properties. Inside the config file I could specify the run environment and all worked nicely.
I am looking for a way to use one or more properties to build the namespace declaration on the fly so that my tests will support multiple environments.