Hi Giscard,
Thank you for your reply.
I had already done all that you suggest. This is not the problem.
Before I was trying to run from the command line, I did not need to use any custom project properties to successfully run my test suite from each of the environments. I created the default environment (as you say) with NO custom properties. I then went to the Environments tab and created 4 environments (using the "Copy endpoints & credentials from the project") and then changed the endpoint for my service for each of the 4 environments. Again, no custom properties were in play here and the test suite ran from each of the 4 environments using the proper endpoint (defined at the project level for each of the 4 environments). I understand how to do this when not using a custom project property for the endpoint.
Later - I needed to be able to run my test from the command line. So I then added the custom project property CPServiceEndpoint (on the Overview tab). I then went to each of the 4 environments and entered ${#Project#CPServiceEndpoint} as the value for the CPServiceEndpoint. Then I tested passing the value for CPServiceEndpoint via the command line and this works fine for each of my 4 environments.
The problem came in after adding the CPServiceEndpoint custom project property and NOT executing the test suite from the command line. I have a different value that I need to pass to the CPServiceEndpoint for each of the 4 environments. Easy to do with command line. I am stuck with how to do it from within SoapUI. (I have tried creating a 2nd custom project property to hold the value I want for each of the 4 environments and then transferring this 2nd project property into CPServiceEndpoint, but this doesn't work.)
Does my question make sense?
Thanks,
Kelli
