SilkTest Question 51: How to conduct testing with SilkTest via Microsoft Remote Desktop?

To execute testing the SQA Engineer needs to install SilkTest on the remote machine, but during exertion of automated test cases SilkTest would treat via Microsoft Remote Desktop windows as the GUI application under test. It means that in case you minimized or exit desktop window the SilkTest Agent cannot control anymore the mouse and keyboard and test cases would fail. Remote Desktop can only be used for automated testing when it is non-minimized. Of course there is some work around: connect via Remote Desctop session into first test machine and from that machine hook up into machine with SilkTest installed. Then when someone closes Remote Desktop from the first machine, the remote machines session would stay open. It is weird solution, but it work in our QA Lab environment.

7 comments:

Chan Ho Sang said...

I am using pcAnywhere to access the remote server in order to run the SilkTest. However, the response time are really slow compare to remote desktop. I won't use it for developement for sure.

Your solution sound great. Why never thought of that? Thanks.

Anonymous said...

1) How to connect Linux Machine from a Windows Machine using Silktest.?
I have install Linux agent on the Linux machine. but not able to connect the machine.Please mention the Steps to establish the connection between the Windows machine and Linux Machine.

Thanks in advance.,

MP said...

Check if Unix is using the SilkTest Unix Agent default port (2965) for another process and that port is open

David Genrich said...

I have all my tests machines in a diffrent state (and for some on my team, a diffrent country). We use Remote Desktop for all the testing. And, we do it without having RD open (unless we are developing, or testing a test where we want to see it).

For an actual test through, I created a vb.net application to pick the project and test we want to run as well as our property file for which stack to run the tests against. The vb.net app will then set Windows to auto-login, and create a WSH script to run at login. Then, the system reboots - which closes the RD session. The sytem reboots, automatically logs in, and starts the WSH script. This script then turns auto-login back off, and starts the desired Silk test. When Silk ends (by completing the test, or do to some un-catched failed), the WSH sends an email out that Silk finished.

As you can see, I am using multiple tools to solve this problem - Silk, vb.net, and WSH. No reason we have to do everything in Silk. Use what you can to achive what you need.

Enjoy,
David Genrich
E2open

MP said...

Thanks for input David

Vishal G said...

Have used VNC to connect in past, and it worked vs. using Remote desktop(RDP)

Vishal G said...

Have used VNC to connect & execute test cases vs. using Remote Desktop(RDP)

SilkTest interview questions for QA Testers