This functionality is supported only if you are using the Classic Agent.
Using the basic workflow, Silk Test Classic can automatically enable extensions for many different development environments. If you would rather enable the extension manually, or the basic workflow does not support your configuration, follow the steps described in this topic.
A target machine is a system (or systems) that runs the 4Test Agent, which is the software process that translates the commands in your scripts into GUI-specific commands, in essence, driving and monitoring your applications under test. One Agent process can run locally on the host machine, but in a networked environment, any number of Agents can run on remote machines.
If you are running local tests, that is, your target and host are the same machine, complete this procedure and enable extensions on a host machine manually.
If you enable support for ActiveX in this dialog box, make sure that it is enabled in the Extensions dialog box as well.
Once you have set your extension(s) on your target and host machines, verify the extension settings to check your work. Be sure to consider how you want to work with borderless tables. If you are testing non-Web applications, you must disable browser extensions on your host machine. This is because the recovery system works differently when testing Web applications than when testing non-Web applications. For more information about the recovery system for testing Web applications, see Web applications and the recovery system. When you select one or both of the Internet Explorer extensions on the host machine’s Extension dialog box, Silk Test Classic automatically picks the correct version of the host machine’s Internet Explorer application in the Runtime Options dialog box. If the target machine’s version of Internet Explorer is not the same as the host machine’s, you must remember to change the target machine’s version.