Forum Discussion
AlexeyKolosov
13 years agoStaff
Hi Ronald,
You can use the following approach:
1. Install TestExecute on the virtual machine.
2. Instal PsExec from PsTools on the host machine from which the test is going to be started. The installation can be obtained here:
http://technet.microsoft.com/en-us/sysinternals/bb897553
3. On the host machine, create a script which will launch PsExec in order to invoke TestExecute on the remote machine with the needed command line parameters. Note that the virtual machine must be turned on at the moment you start PsExec (which, in its turn, will start TestExecute on the VM). You can use sample script provided in the following How To entry to make TestComplete/TestExecute on the host PC execute the custom command line:
Get an application's exit code
As an alternative, you can simply create a .cmd (or .bat) file, specify the command line in that file and launch that file instead of writing a script for that.
You can use the following approach:
1. Install TestExecute on the virtual machine.
2. Instal PsExec from PsTools on the host machine from which the test is going to be started. The installation can be obtained here:
http://technet.microsoft.com/en-us/sysinternals/bb897553
3. On the host machine, create a script which will launch PsExec in order to invoke TestExecute on the remote machine with the needed command line parameters. Note that the virtual machine must be turned on at the moment you start PsExec (which, in its turn, will start TestExecute on the VM). You can use sample script provided in the following How To entry to make TestComplete/TestExecute on the host PC execute the custom command line:
Get an application's exit code
As an alternative, you can simply create a .cmd (or .bat) file, specify the command line in that file and launch that file instead of writing a script for that.
Related Content
Recent Discussions
- 2 days agoMW_Didata