A custom test type integrates your non-OpenText testing tools with Application Lifecycle Management (ALM). After implementing and deploying a custom test type, you can use ALM to configure the testing tools you are using, view test scripts created, execute the tests across multiple remote hosts, and view test results.

Without any customization, ALM enables integrated use of several test types based on OpenText testing tools such as Unified Functional Testing, and LoadRunner. For example, it enables test types LR-SCENARIO, MANUAL, SYSTEM-TEST, and others. From within ALM, tests of these types can be planned, managed, and run, the results can be viewed, and the tests can be linked to requirements and defects.

This guide explains how to achieve a similar level of integration with other testing tools by defining and implementing custom ALM test types that use those tools, and registering the test types with ALM. 

You can save more information to the ALM project to achieve a greater degree of integration with ALM. For instance, you can save the parameters used for each test, details of test results, or planned and actual settings and parameters. To save this information, use the tools provided by the ALM REST API or the Open Test Architecture API (OTA) when implementing your custom test type.

For more information about the REST API or OTA, see the Documentation Library in ALM.