Installing a Custom Test Type > Deploying Test Type Files

Deploying Test Type Files

The following instructions apply to the Custom Test Type files: The IScriptViewer, IExecutionConfigurationViewer, IResultViewer, and ITestTypeImageProvider classes.

When you reference OTAClient.dll in your Visual Studio project, a file, Interop.TDAPIOLELib.dll, is generated as a COM wrapper. Include Interop.TDAPIOLELib.dll in the deployment of your test type along with the components you create.

The deployment method of the testing tool depends on the tool and is not discussed in this guide.

Note: The installations of the Remote Agent and the testing tool always require administrator rights on the client machine and cannot support side-by-side use of different versions. They must be deployed and registered on the client machines.
You can use any deployment method, including deploying them together with ALM. If you deploy the tool and/or the Remote Agent with ALM, follow the instructions for the Test Type installation: Deployment: Administrator's rights without side by side support.
You can deploy the Remote Agent and/or the testing tool without side-by-side support and still deploy the Test Type for side-by-side use.

If your Test Type is not expected to be deployed in more than one version at a time and the users of the client computers will have administration rights, follow the instructions in Deployment: Administrator's rights without side by side support.

If you want side-by-side support or the client users will not have administration rights, follow the directions in Deployment: Administrator's Rights with side by side support.

For other configurations, search for knowledge-base articles on the HP Support Web-site.

 

Next: Registering Custom Test Types with ALM


© 1993 - 2013 Hewlett-Packard Development Company, L.P.