Project Property manipulation
Hi Admin We use web based tool for doing daily smoke testing of our web services. The web based tool is also used by developers to kick off tests manually by selecting 2-3 choices. One of the ch...
Forum Discussion
Thanks @mnrao for taking time to understand the issue and giving solution on that lines.
I understand what you are saying. I was thinking on similar lines after posting this question. I would like to confirm you that we are already using project property variables in order to make endpoints generic.
Can you shed some light on why do you think we would require separate property files?
What I am thinking is to have single common property file created each time. Our tests work as follows:
1. User initiates tests using web interface
2. Request comes to shell script for processing. There I can build property file and create at a specific location shared by all test projects
3. In the soapUI project load script, load project properties from the property file
3. Use property values to take certain decisions in the project load script.
4. All endpoints anyway using project property variables
When user wants to run tests in the tool itself, project load script will use default project properties (may be can load default properties again from a property file). Environments feature would be used to run tests on various environments.
How it sounds?
I understand what you are saying. I was thinking on similar lines after posting this question. I would like to confirm you that we are already using project property variables in order to make endpoints generic.
For each environment, will maintain separate property file.
Can you shed some light on why do you think we would require separate property files?
What I am thinking is to have single common property file created each time. Our tests work as follows:
1. User initiates tests using web interface
2. Request comes to shell script for processing. There I can build property file and create at a specific location shared by all test projects
3. In the soapUI project load script, load project properties from the property file
3. Use property values to take certain decisions in the project load script.
4. All endpoints anyway using project property variables
When user wants to run tests in the tool itself, project load script will use default project properties (may be can load default properties again from a property file). Environments feature would be used to run tests on various environments.
How it sounds?