Multiple Testing Environments - Database Connection Strings
Posted: Wed Mar 04, 2015 8:54 pm
Hello,
We have multiple environments in which automated testing is taking place (Dev, QA, Training) and so I have been maintaining the same test suite on each, as well as adding it to any new environments that it's not on yet. Each uses it's own database (SDEVSQL, SQASQL, STRAINSQL) and so this makes using and updating the same test suite in each environment much more difficult due to different connection strings.
This is an issue because the test suite covers multiple applications and is very large, complex, and constantly growing. Because of this, any time an addition to the suite is made (or in the case the whole test suite needs copied to the new environment), it can become a huge pain to change everything over to point to the right database, as there are a lot of SQL connectors.
My question is this: Is there a way that I can use the exact same test suite in each environment, but just set a flag or variable before executing that contains the name of the relevant database so that it can be used in the connection string for all the sql data connectors in the suite?
Or, is there simply another way to copy the whole test suite over and easily change all of these connection strings without having to manually go through every SQL connector and change it in the settings?
Thanks!
We have multiple environments in which automated testing is taking place (Dev, QA, Training) and so I have been maintaining the same test suite on each, as well as adding it to any new environments that it's not on yet. Each uses it's own database (SDEVSQL, SQASQL, STRAINSQL) and so this makes using and updating the same test suite in each environment much more difficult due to different connection strings.
This is an issue because the test suite covers multiple applications and is very large, complex, and constantly growing. Because of this, any time an addition to the suite is made (or in the case the whole test suite needs copied to the new environment), it can become a huge pain to change everything over to point to the right database, as there are a lot of SQL connectors.
My question is this: Is there a way that I can use the exact same test suite in each environment, but just set a flag or variable before executing that contains the name of the relevant database so that it can be used in the connection string for all the sql data connectors in the suite?
Or, is there simply another way to copy the whole test suite over and easily change all of these connection strings without having to manually go through every SQL connector and change it in the settings?
Thanks!