Hi Kateryna,
So, if I understood correctly, it is possible to run tests using TestExecute on the other computer if all tests are located there and I will run this script to change connection string for the each db checkpoint. |
Yes. Just make sure that each computer has the needed database provider installed.
But I have the last question: do I really have to put the exact name of the machine in the Data Source. Can I put there some name that will fit all machines? Like localhost or something??? |
If you use a network database server, there is no need to change the connection string at all, because it's the same on all client computers. So, you can simply use the originally configured DBTable item.
If you use local data sources (located on the same computer where the tests are run), it is recommended to move them to some network location to avoid computer-specific data in scripts. For example, instead of storing an MS Access .mdb file on each test computer, place it to a network share.
However, if you need to use local data sources, there're some tips that can help you make scripts computer-independent:
* Your database provider may support specific syntax for local data sources. Please refer to
http://connectionstrings.com to learn the connection string syntax for your provider.
* If the connection string includes the local computer name, use Sys.HostName in scripts instead of the hard-coded computer name.
* If the data source file is in the project folder, you can use Project.Path in scripts to specify the project folder path.
Hope this helps!