You can either set up error messages in your batch file as it shows in the example, or you can rerun the test in TestComplete and view the error log.
Marsha_R thnk you for the updates .
Where those errors are posted ? As shown in the example
:NotEnoughDiskSpace
ECHO There is not enough free disk space to run TestExecute
GOTO End
Where the errors There is not enough free disk space to run TestExecute are posted ?
echo command causes the output to go to the screen. You would see
There is not enough free disk space to run TestExecute
on your screen whereever it is that you ran the batch file. That may not be convenient so you could add code to the batch file to write the message to a file somewhere.
Keep in mind... The batch files runs TestExecute... so TestExecute doesn't have any visibility as to what the batch file does... You will need to set up some sort of monitoring process to track what is going on with the remote executions.
you are right.
This is what we have been trying to get. Right now we are running our testcomplete scripts on testexecute machine using batch file and Task scheduler. Once we disconnect from testexecute machine we do not have the process to know the status of the TestExecute whether it fail to launch or whether the machine ran out of memory.
This is where investing in a tool like QAComplete, Jenkins, or some other similar CI tool is good. TestExecute is the remote engine to execute the tests, but the other tool is the monitoring tool to determine the current state of the test execution.
