QC Scheduler, Virtual Machine, and cscript
Using CruiseControl, we connect to several different Virtual Machines which run a variety of different test suites we have in Quality Center. The results are then sent back to CruiseControl for the developers and upper management to see what is and is not working with our daily builds.
The problem that we have is an inability to launch the scheduler on the VM's when called from our .vbs app. We've been using a 3rd party application called RunTestSet.exe. When utilizing the RunTestSet.exe, there is no problem. When we attempt to perform the same scenario using our .vbs app, the vm's will hang. Apparantly, there is a problem with running cscript/wscript @ the same time as running QC's SCheduler on the VM's
When we run them on our local pc's, the delay/machine lock up is not experienced. It only occurs when we run them on the VM's.
I am curious to know if anyone else runs QTP scripts via QC's scheduler on Virtual Machines and whether or not they use an .exe to launch or not.
Re: QC Scheduler, Virtual Machine, and cscript
Found the problem:
When executing the section While test running, wait .. we left out the wait part and only had it continually checking the status of the run. This impacts performance on the VM's because they run so much faster than our desktop PC's.