Forum Discussion

johandelaat's avatar
johandelaat
Occasional Contributor
9 years ago

activeEnvironment in Jenkins is not environment set in the command line using the -E paremter?

I'm using Ready! API 1.3.1 SoapUI NG PRO. In some of the testcases I'm using a variable env to know in which environment I'm working. def env = testRunner.testCase.testSuite.project.activeEnvironme...
REST
johandelaat's avatar
johandelaat
Occasional Contributor
9 years ago

Hi Tanya,

 

First line of my post :

I'm using Ready! API 1.3.1 SoapUI NG PRO.

So yes the PRO license was activated.

The fact that the correct endpoints are used proves for me that the parameter -E works correctly.

 

We've downgraded to the version 1.3.1 because in version 1.4.1 the authorization is seriously f**cked up.

It caused us a lot of useless rework of the testcases.

So NO I will not check if there is the same behaviour in 1.4.1.

 

Do you have any idea if there is a workaround for activeEnvironment to find out which the environment is?

How can I get the value set by the -E parameter?

 

Johan

 

  • TanyaYatskovska's avatar
    TanyaYatskovska
    SmartBear Alumni (Retired)
    9 years ago

    Hi Johandelaat,

     

    It makes sense to add the /i command-line parameter in addition to /E. This will load some more UI classes that testrunner should use.