Forum Discussion

emmanuelflores's avatar
emmanuelflores
Occasional Contributor
8 years ago

Loading or referencing environment properties

Hello, I'm new to Ready API and SOAPUI NG in general. We're still trying to figure out best practices for various thing, in particular VCS. Our tests require a username password, however, we don't wa...
  • gilugopi's avatar
    gilugopi
    8 years ago

     

     

    Actually Global Properties work well with environments

    And Environment settings are not under settings.xml, its under each projects xml file

     

     

    Lets say you create two different global properties

    envAPassword :  envAPasswordValue

    envBPassword :  envBPasswordValue

     

    Now you need a password property at the project level to show up in environments, let's call it projectPassword

     

    You need to environment settings

    1. select envA and need to specify projectPassword value as ${envAPassword}

    2. select envB and need to specify projectPassword value as ${envBPassword}

     

    Thus global properties flows seamlessly into your environment.

     

     

     

     

emmanuelflores's avatar
emmanuelflores
Occasional Contributor

I didn't realize there were global properties as well, however I'm not sure it'll work out for Environments settings. If we want to switch from envA to envB, we need to reference the credentials for envB. 

 

This does lead me to wonder if not checking in the settings.xml file for a Project would have the same impact. It seems like that's where the environment settings are saved.

gilugopi's avatar
gilugopi
Contributor
8 years ago

 

 

Actually Global Properties work well with environments

And Environment settings are not under settings.xml, its under each projects xml file

 

 

Lets say you create two different global properties

envAPassword :  envAPasswordValue

envBPassword :  envBPasswordValue

 

Now you need a password property at the project level to show up in environments, let's call it projectPassword

 

You need to environment settings

1. select envA and need to specify projectPassword value as ${envAPassword}

2. select envB and need to specify projectPassword value as ${envBPassword}

 

Thus global properties flows seamlessly into your environment.

 

 

 

 

  • emmanuelflores's avatar
    emmanuelflores
    Occasional Contributor
    8 years ago

    Makes total sense and works as expected. Thank you for taking the time to help.