Forum Discussion
You could save the batch file pretty much anywhere so long as the user that is running the task has access to the location.
Ok I got some sucess .
Here are few concerns
1. For different project Suites do we have to create different batch files - mean each batch files for each project
suite ?
2. If project suite contain multiple projects/TestItems in each projects then how do we know to set up the time
interval ?
3. Since TestExecute machine is on VM which can be accessed using Remote desktop then how task scheduler
works if
a) we miniize the Remote desktop window
b) we close the Remote desktop
c) how can we see the reuslt fo batch file
- 1. I would create one single batch file that calls all the projects
- 2. You can set windows task scheduler to let the running instance finish before firing off a new one
- 3. You can miminize but not close the RDP connection. There HAS to be an active user session for GUI tests to run. You can specify where to save logs from the command line and save then on a network share for example.
How will you include multiple projects in different suites in a single batch file ? do you hav sample or example ? I can only see the example of one project in Testcomplete documentation .
https://support.smartbear.com/testcomplete/docs/working-with/automating/command-line-and-exit-codes/exit-codes.html
Per the documentation above, you can specify the .pjs file and it should run every project in the file.
You could also specify each project individually insuccession.
file_name
Launches TestComplete and loads the specified project (.mds file) or project suite (.pjs) into it