As part of my automation I have a an XML embedded within the solution which dictates the database source along with username/password. As I start to execute many different configurations over remote agent I was wondering if there was a clever way of incorporating the changing of where this is pointed at as part of the test? Putting something like that in the setup would reduce time and the risk of running tests against the wrong database.
Has anyone done anything like this before?
Ask general questions here.
2 posts • Page 1 of 1
- databaseconfig.png (41.06 KiB) Viewed 87 times
You could write a code module that runs during a [Setup] block which updates this XML file ahead of any tests that require it. You could parameterise this code module to fine-tune the adjustments it makes to the XML file. And then data-drive the test-case/smart-folder with these parameters so it gets modified multiple times.