A smart way to handle data when using environment prop?

Hi,

Environments in general are to hold different configurations for the SoapUI project, you may have a "test" environment and a "production" environment for example. I do not know what exactly you are trying to accomplish, but if you are going to have a lot of properties then you may want to look at property expansion which will allow the properties to be dynamic.

Here is a link to that content:
http://www.soapui.org/Scripting-Propert ... nsion.html


Regards,
Marcus
SmartBear Support

I agree.

If you have a test case where you are searching for a customer, and it is going to be executed in two different environments, you might also need to have two set of data.
The easy way, is to create a #project# property. Because I am using environment, It is possible to add different value into each environment property.

In your teststep, you just add the property and it is working fine on different environments.

In your link, I can see an #env# property, but I don’t know where it is stored.

In my project file, I have right now 2 test suites and totally 25 test steps.
If I continue add my test data into a project property, I think the property easy can explode.
May be that is okay, as long as I remember to have a naming convention.

So I am just asking if there are any other 'easy' ways to set up the data driven test when using environment?

Hi,

The #env# is used for environment variables. If you have a separate set of data for each environment then you should look at using a DataSource and DataSink and use a dynamic property to determine the file to read from and write to depending on what environment is in use.

Please see this link on data driven testing:
http://www.soapui.org/Data-Driven-Testi ... tests.html


Regards,
Marcus
SmartBear Support