Forum Discussion
Ivan_Trampedach
12 years agoContributor
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?
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?