Using an INI file stored in the project suite
I am hitting a stumbling block here. I have an INI file that I created from within TestComplete using the Storages object to export and save some variable settings. I was able to add the file t...
Forum Discussion
We are on a Windows Domain, the computer names are not really important because the ini file was on a shared network drive.
Since we run TestComplete in RDP because of the system where it is installed at and we only have one node locked license. We are also licensed for TestExecute. We were looking for a solution to be able to have 2 testers run the automated tests at the same time. But because of some preset variables they would be running the tests with the same data and screw up one test or another.
So the thought of being able to A) copy the file with the suite so the settings could be changed per suite sounded appealing. B) the other possibility was machine dependent. Where I have the script which is on a mapped drive point to a local drive ( eg. C:\ ) that way everyone has a C:\ drive then all they need to do is copy the INI file to be able to have different testing variables and not mess with another's test run.
This is because unless the values were changed in TestComplete before running it in TestExecute the copied suite would still have the same variables as the previous suite and screw the automate test up for both testers.
Since we run TestComplete in RDP because of the system where it is installed at and we only have one node locked license. We are also licensed for TestExecute. We were looking for a solution to be able to have 2 testers run the automated tests at the same time. But because of some preset variables they would be running the tests with the same data and screw up one test or another.
So the thought of being able to A) copy the file with the suite so the settings could be changed per suite sounded appealing. B) the other possibility was machine dependent. Where I have the script which is on a mapped drive point to a local drive ( eg. C:\ ) that way everyone has a C:\ drive then all they need to do is copy the INI file to be able to have different testing variables and not mess with another's test run.
This is because unless the values were changed in TestComplete before running it in TestExecute the copied suite would still have the same variables as the previous suite and screw the automate test up for both testers.