Hey ravienu
Have you thought about dumping the 'Environments' functionality and just using a project level properties file instead? I tried setting up multiple environments a while back and had trouble - then Rao suggested using a properties file instead.
What I mean is, I setup a project's tests, but I'm able to switch environments by loading in an environment specific project level properties file before execution begins. I have a .properties file - 1 for each environment.
All my environment specific variables/parms (usernames, passwords, tokens, URLs, URIs) go into my properties file. I just load it in before execution and I've parameterised everything in my tests to source those project level properties. Works brilliantly! I don't even bother with the Environments functionality cos it works so well.
I know it isn't the answer you were hoping for, but it's a workaround to your issue.
ta
Rich
Thanks richie ,
Yeah seems you are correct, looks like using properties file is a good idea. I will change to it in sometime. But unfortunately I dont have that much luxury now as our testing phase in progress.
Hi nmrao , could you please suggest some quick solution for my issue for now.... Thank you very much.
Cheer's
Ravi..
