Hey
Mahesh9100,
Yes this is totally feasible and in fact is the way i build all my readyapi projects now.
The way i do this is that i create a ptoperties file that contains my environment specific static data, such as URLS, token values, username/password values and within this properties file i have placeholder property names (without the values populated) for all my dynamic data that is environment specific such as GUIDs etc.
I create one of these properties files for each environment.
Before execution i determine which environment is being tested and i then load in the properties file (which creates custom project level properties....as i already stated...the static data properties and values specific to the environment and empty/blank custom project level property placeholder names).
Once the file is loaded in, i then have some disabled testsuites that execute queries against the environment to populate those dynamic data values (that are environment specific).
Within my project i then create my normal functional testsuites (that are enabled) to exercise my tests, but the first testcase includes a single "Run Testcase/teststep" that executes the disabled testcase that generates the dynamic data (this wa the dynamic testdata never has the chance to expire). The remainder o my testcases are normal testcases except they alwaya reference the custom level project level properties for the all environment specific detail.
The above works really well and do it or every single readyapi project i create now. Alas i cant take credit for this approach. It was
nmrao who showed me how to do this and it works like a charm.
Obviously this cant be the only way of doing this, but this approach works so well for me, ive never bothered using any other or even learning any other approach.
Cheers
Rich
