Forum Discussion
tristaanogre
11 years agoEsteemed Contributor
As mentioned in my reply on my other post, because there is a "Local Value" on persistent variables, you need to populate that value locally. It's not something that persists across network shares. The "persistant" has to do with persisting between runs on the same box.
As noted, you can use the Storages object to create and populate INI, XML, or other similar files that will allow you to set values based upon locality. This has worked very well for me in the past. It's even automated in that your master machine which you use to launch the tests can write out the INI file that then the remote machines use to read it in. And, once the remote machines read it in, you don't have to re-open the INI... it will be populated in the Persistant Variable.
Give me a bit of time, I can even get the script code written up but that should be a good way forward to transfer settings across boxes. Heck, just take Ryan Morgan's code and, instead of assigning static values, read the values in from keys in an XML file organized by machine name.
As noted, you can use the Storages object to create and populate INI, XML, or other similar files that will allow you to set values based upon locality. This has worked very well for me in the past. It's even automated in that your master machine which you use to launch the tests can write out the INI file that then the remote machines use to read it in. And, once the remote machines read it in, you don't have to re-open the INI... it will be populated in the Persistant Variable.
Give me a bit of time, I can even get the script code written up but that should be a good way forward to transfer settings across boxes. Heck, just take Ryan Morgan's code and, instead of assigning static values, read the values in from keys in an XML file organized by machine name.