NOTICE: Our Community is moving. Get more information.
SilkTest"s performance is affected by a number of conditions. If you are finding that SilkTest is slowing only on certain applications, then this is an indication of a timing problem with communications for that particular application. You can set values for the keyboard and mouse event delay in the Agent Options window.
When SilkTest performance is poor across the board, this usually indicates that either
1) SilkTest is using an old DLL from a previous version that wasn"t deleted because the machine wasn"t rebooted after uninstalling the old version,
2) there is a conflict with another application that is using the same single-point-of-entry Windows API function call that SilkTest uses to inject into applications.
If you had an old version and don"t remember rebooting after uninstalling it, then uninstall the current version, *reboot*, and install again. The reboot will unload the old DLL.
If you have a conflict with another application, you will need to step through running applications or processes one by one, killing them off and seeing if SilkTest"s behavior changes back to what you expect.
This single-point-of-entry WIN32 API function call is only made by applications that need to either inject or inspect all other applications or files on a machine. So, typical applications that won"t work with SilkTest are virus scanners (because they look at every file), security mechanisms (that keep a trace of activity) and performance enhancers (because they frequently look for routines to optimize.