I want to be able to run my tests over night in multiple environments. For this purpose I have created a batch file to trigger the test run and scheduled it in each environment.Because I want to run on multiple environments I chose to RDP into each of them from my local machine (test development machine) one after another and get the runs finished. For this I scheduled all the RDP connections into each environment on my local machine.Now as I said in beginning, the intention is a over night run and I want to come and check the results in the morning.I know that TC does not interact with the GUI if the machine is locked and the suggestions that are given for this are either to RDP into the locked machine or to use virtual machine. What if the the machine that is attempting to RDP itself is locked? Obviously I cant keep my machine unlocked over night plus the companies security policies would not like that.What do I do now? - I want the over-night run with out any human intervention when all the machines are locked. (Overnight run in true sense).

Answering myself:I used a batch script to unlock my machine automatically and rdp into the desired test environment. Scheduled to run the batch at the time of running the tests. Scheduled the testcomplete scripts batch on each test environment in sync with the rdp connection time.Let me know if there is a better approach.My batch file: (Runs fine of Win XP and Win Server 2003)@ECHO offREM Auto Login into my machine at the time of the nightly run schedule if the system is lockedREM For the following line to work logon.exe utility should be present at the locationREM logon.exe utility can be downloaded from http://www.softtreetech.com/24x7/archive/51.htm"D:\Automation utilities\logon.exe" -u username -p passwordREM RDP into TESTENV01REM For the following line to work TESTENV01.rdp file should be present at the locationREM TESTENV01.rdp can be created form mstsc.exe using the necessary setting like the username password etc and then > SaveAsSTART "" "D:\Automation utilities\TESTENV01.rdp"REM Delay the batch execution for 10 seconds to allow the RDP to connectPING 1.1.1.1 -n 10 >NUL:STARTREM Keep checking if RDP conection to TESTENV01 is closed by dumping the result of appropriate filter on TASKLIST into a text file and search for the text mstsc in it.TASKLIST /svc /FI "WINDOWTITLE eq TESTENV*" /FI "STATUS eq running" /FO csv >temp.txtTYPE temp.txt | FIND /i "mstsc"ECHO Error Level = %ERRORLEVEL%IF ERRORLEVEL 1 GOTO NOTRUNNINGIF ERRORLEVEL 0 GOTO RUNNING:NOTRUNNINGECHO No active RDP connection(s) to TESTENV01 existGOTO LOCKSYS:RUNNINGECHO Active RDP connection(s) to TESTENV01 existREM If connection to mstsc is running wait for 3 seconds and resume checkingPING 1.1.1.1 -n 10 >NULECHO Wait of 3 seconds finished. Starting the check again...GOTO START:LOCKSYSECHO Deleting the temp files...DEL temp.txtECHO About to lock the system....rundll32.exe user32.dll, LockWorkStation

One more possible solution is to use NetworkSuite. You can create a master project with NetworkSuite project item and use it to login to remote computers and launch your tests there.

Pavel,Help Says, "It is possible to run tests on locked computers using network suites;locked computers being slave hosts. However, this approach requires thatTestComplete is installed on both the locked computer and the computer that willinitiate the test run."In my case I want all the systems to be locked state when the tests get triggered. So even if I use network suite, I would end up writing another batch to wakeup the master computer plus the fact that I work on a VPN with the test machines sitting in different geographical locations that I access using RDP normally. I tried to connect to the machines on VPN using network suite but had no success. Not sure If I missed out on something or the TestComplete's network suit does not support connections to VPN-ed systems.Thankyou

Hi Ahmed,As fas as I understand, the current problem is that your master machine cannot connect to slave machines using the Network Suite features. Since it does not matter for TestComplete whether the remote machines are machines on your LAN or machines accessed via VPN, the problem should not be related to the way you connect to them (unless your VPN connection is broken). First of all, take a look at the following SQAforums thread, it contains a number of steps you should try too:http://www.sqaforums.com/showflat.php?Cat=0&Number=610518&an=0&page=0&gonew=1#UNREADAlso, I recommend that you see the "TestComplete Network Activities - Possible Issues With Antiviruses" help topic.

I am sorry to dig up an old thread, but I am having excatly the same dilemma as the OP describes.At my work place, it is mandatory to lock computers, when you leave your workstation. Due to this, I am having trouble seeing how it is possible to launch any tests, may it be from TestComplete or TestExecute.Only solution I see, and it's an ugly one, is using the OP's login.exe tool to force a login on my workstation, and then run a script that starts the test via command-line.Can it really be true, that you cannot execute tests, without actually leaving your workstation unlocked and unguarded?And yes I know you can use the build-in network suite of TestComplete to launch tests, or use RDP. But you cannot initialize any of these actions, from a locked PC over night.We have recently purchased several floating enterprice TestComplete licenses, and I am baffled that this cannot be done. If this is true, our licenses are basically worthless.Please give me some good news guys.

Over Night Test Runs | SmartBear Community

11 Replies

Pavel_1
Contributor
15 years ago
Hi Daniel,

The details on how to organize overnight test runs depend on how your build and test processese organized and test environment.

But I'll try to explain in general how to do that.

1) Create a batch file that will execute test (and optinally make some preparation operations like update test sources from version control, copy latest builds, kill existing testexecute processes as they will prevent launching tests etc, you can also add logoff in the end to completely log off from the test machine after test).

2) create an .rdp file on another machine, it should connect to your test machine via rdp:

Start->Run - mstsc, or Start->All Programs ->Accessories -> Remote Desctop Connection. Make all settings you need (mark the password to be saved) and then save the rdp file - 'save as'. Make sure that doubleclicking that file invokes remmote desktop automatically

You can just set 'start program on connection' there to launch batch file from the step1, but it didn't work for me everyehere (at least it didn't on Vista and Windows 7 due to some strange bug), so if it won't for you you may use psexec utility to launch process remotely in the rdp session.

3) Create batch file that launches this rdp file, and then (optionally, if 'launch program on connection' won't work) executes your test in remote session interactively with psexec (you should specify correct session number after 'i' parameter there).

4) Put it on schedule e.g using standard windows task scheduler.

In my case the tests are triggered from build server after the nightly builds are ready - I made this with a separate automated build studio macro, but that's already another story...

Regards,

Pavel

Forum Discussion

Over Night Test Runs

11 Replies

Recent Discussions

Unable to activate floating license.

Testcomplete closed itself

log message issues in testcomplete

Related Content

Embed "night" tile border

Splitting a project to run a daytime and night time test

Dashboard "Night Mode"