Forum Discussion
SmartBear_Suppo
10 years agoSmartBear Alumni (Retired)
Hi,
When you are using the TestRunner you are overriding the the endpoint project property.
To do this when you run your test from the SoapUI Pro interface, you would have to change the value that is currently set for that project property in the environment you are using.
The concept of overriding a property doesn't quite work the same way in the graphical user interface, as the environment choice itself is meant to be able to override some set project properties, and you pre-define that in the environment.
Instead of having a second property "X" that you transfer to CPServiceEndpoint, why not have an environment for each such endpoints "X"? From your perspective they would be sub-environments of "QA", for instance, QA_1, QA_2 each with it's CPServiceEndpoint that refers to the correct X endpoint value needed for your QA tests. Could this work for you?
Regards,
Giscard
When you are using the TestRunner you are overriding the the endpoint project property.
To do this when you run your test from the SoapUI Pro interface, you would have to change the value that is currently set for that project property in the environment you are using.
The concept of overriding a property doesn't quite work the same way in the graphical user interface, as the environment choice itself is meant to be able to override some set project properties, and you pre-define that in the environment.
Instead of having a second property "X" that you transfer to CPServiceEndpoint, why not have an environment for each such endpoints "X"? From your perspective they would be sub-environments of "QA", for instance, QA_1, QA_2 each with it's CPServiceEndpoint that refers to the correct X endpoint value needed for your QA tests. Could this work for you?
Regards,
Giscard