Forum Discussion
Sorry for the confusion.
- nmrao8 years agoChampion Level 3Ok. testrunner will inject the envrionment name that you needed from command line.
And you already know how to access environment name in the groovy script based on the link you provided in the question i.e.,
testRunner.testCase.project.getActiveEnvironment().name
Hope it is clear and no confusion.- stef8 years agoOccasional Contributor
I don't think that statement
testRunner.testCase.project.getActiveEnvironment().name
is not correct.
I have the feeling that the value saved in the project-url is overwrting the value on the command-line.
I'll do some more testing.- Radford8 years agoSuper Contributor
I'm not sure if this is relevant or not, but quite a while ago I raised a very similar sounding issue with SmartBear support about the -E command line parameter being ignored. SmartBear support responded with:
"I was able to reproduce the issue on our end. I will create a bug once our developers approve, The logs are not updated but fortunately it takes the environment variables even if the log shows a different active environment. Thanks a lot for bringing this issue."
This issue was logged with the internal defect number SOAP-1741.
Please note, I raised this issue with a very old version (SoapUI Pro 5.1.1) but because 95% of our tests were run in a single environment and the fact that no date could be given for a fix we got in the habit of saving our projects in the "correct" environment as a work around. I've actually no idea if this has been fixed or not.
It might be an idea to raise an issue with SmartBear support (If you've got time to burn you could check through all the release notes).
Please post any follow up from support here as I'd be interested to know.
Related Content
- 2 years ago
- 3 months ago
Recent Discussions
- 5 hours ago
- 6 hours ago