Creating .NET Custom Test Types

Creating .NET 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 .NET 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 the remote agent in .NET and expose it to DCOM. You can also create the remote agent with native COM languages, such as Visual Basic or C++.

A test type is one or more assemblies 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 .

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.

See Creating the Remote Agent

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. To implement, create a C# Class Library project named TestType.

Required libraries.

In addition to the TestType class, the custom test type includes an image provider and may include any or all of the optional components:

ITestTypeImageProvider Interface

Get the icons for the test type. This component is required.

IScriptViewer Interface

Shows the test script. This component is optional.

IExecutionConfigurationViewer Interface

Configures the testing tool. This component is optional.

IResultViewer Interface

Shows the test results. This component is optional.

For sample code of the .NET classes, see "Custom Test Type Example".

See also Installing a Custom Test Type.


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