Hi, here is the problem I'm trying to solve:

I am trying to figure out a clean method to allow for multiple test configurations, so that we can easily run a test on webservice host A and products 1, 2, and 3, and then easily run a test on webservice host B and products 4, 5, and 6.

 
I could just hard code methods to set global variables for addresses and product ids, and have the .testrunconfig files update the app.config, so that the test run can look at the app.config and figure out which method to use to set the global variables. One of our constraints is to have the customer to be able to eventually run build and test scripts, as they are managing deployment. Therefore, we need to make the address and product id settings easily configurable by the customer.

Is there anyway to set this up in the testrunconfig setup script? Or should make creative use of the test project's app.config file?
 

Any suggestions would be greatly appreciated.
 

Thanks,

Marcel

marcel_g:

Is there anyway to set this up in the testrunconfig setup script?

That would seem to be the easiest...

One way to make it easier is to load from the test's app.config, but make use of the configSource attribute to allow those settings to really come from another file (put in place by the test startup script).