There shouldn't be any issue; I use a Belkin 2 port all the time. The KVM switch essentially tricks the machine into thinking there's a generic keyboard and mouse on the system, which is all SilkTest can cope with anyway.
A concerned Borland customer, a fly in the ointment, a wrench in the works.
Are you all saying no problems at all
What Brand / Model # are you using?
I did get one reply on the Segue Forum that said:
"I have used both an Belkin and Avocent KVM.
Silk Test performs fine with each during development. During execution of a script, the target machine MUST be the active machine on the KVM. You cannot start a script and then use the KVM to switch to another machine.
At least, I was never able to get this scenario to work. "
This would be a waste of time if you can't switch machines during script runs!
We have never had any issues switching between machines while return SilkTest scripts. We also have pcAnywhere installed on the test machines which we use to test remotely and even that doesn't seem to cause any conflicts.
The only conflict that we've ever had was human-based. Basically it can occasionally be a hassle trying to share 11 machines using one keyboard & monitor.
I think that mine is a Belkin, too. I am definitely able to switch over to another machine while my scripts are running. I also test inside vmware images which further isolates the running image from keystrokes & mouse movements, though. My SilkTest GUI runs in the main machine, though, and I don't have any trouble there.
How do you transition between machines with your KVM? Is there a keystroke combo as opposed to using a button on the KVM? I use the keystrokes and not the buttons. For me, it is Scroll Lock, hold, wait for beep, let go, then hit 1-4.
Chris R Mead
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.