Creating a Custom Test Type

Creating COM Custom Test Types

To integrate custom and third-party testing tools with Application Lifecycle Management, for each testing tool, create a DCOM server implementing the remote agent and a DCOM test type add-in. Then, register the add-in with Application Lifecycle Management. The test type add-in is referred to as the test type or custom test type in this document.

You can create a custom test type with native COM languages, such as Visual Basic or C++. To create the custom test type in .NET, see the ALM .NET Custom Test Type Developer Guide.

A test type is one or more COM components residing on the client that enable Application Lifecycle Management to interface with the data of the testing tool. A testing tool can be supported by more than one test type.

Application Lifecycle Management uses the remote agent and the test type to run tests and display test scripts and execution results created with a custom testing tool. The remote agent resides on the remote testing host and interfaces with the testing tool.

For example, when ALM runs a LoadRunner test, the LoadRunner test type notifies ALM of the LoadRunner remote agent's class ID. ALM can then communicate with the remote agent.

To have ALM download the files required to use your custom test type to the clients, list the files in an INI file; and place the files, the INI file and any manifest files in the download folders as explained in Deploying Test Type .

Register the test type with Application Lifecycle Management by specifying the class ID of the test type class. Specify the ID in the INI file described in Registering Custom Test Types. This identifies the main COM class of the test type. ALM creates an object of this class and uses its methods to interface with the testing tool through the remote agent and the custom ActiveX controls (DLL and OCX files).

To run the custom test type, you must implement the remote agent:

Remote Agent Object

Runs tests locally and remotely. This component is mandatory.

The RemoteAgent must implement the IDispatch interface or dual interfaces, and the IRemoteAgent interface.

Custom test types enable you to execute tests that were created with your own testing tools on remote hosts, and view test scripts and results. Each custom test type must include a TestType class and may include one or more of the optional components:

TestType COM Class Contains the test type general properties. This component is mandatory. For the methods and properties to implement, see "TestType Object"
ScriptViewer ActiveX Control Shows the test script. This component is optional. For the methods and properties to implement, see "ScriptViewer Object".
ResultViewer ActiveX Control Shows the test results. This component is optional. For the methods and properties to implement, see "ResultViewer Object".
ExecConfiguration ActiveX Control Configures the settings for a test instance. This component is optional. For the methods and properties to implement, see "ExecConfig Object".

See also Installing a Custom Test Type.


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