This section provides basic programming information that you need before you develop your Testing Agent:
You must implement the Testing Agent to run out-of-process to ensure that the Testing Agent does not run in UFT One's context.
When you develop your Testing Agent, your project references the type libraries provided by the UFT One Testing Extensibility SDK. The libraries are located in <UFT One Testing Extensibility SDK installation folder>\SDK\Ifs. If you are developing the Testing Agent using Microsoft Visual Studio, register the type libraries using the Windows command:
regtlib <full path of the .TLB file>.The libraries are:
UFT Extensibility Agent type library (AutInterface.tlb and AutInterface.idl files). This library is mandatory.
UFT Extensibility Agent type library (QtpInterface.tlb and QtpInterface.idl files). This type library is required only to support recording. For more information, see Developing Support for Recording.
UFT Extensibility Virtual Object type library (TEAVirtualObject.tlb and TEAVirtualObject.idl). This type library is required only to enable returning a test object from a test object method. For more information, see Returning a Test Object from a Test Object Method.
You can expose the interfaces that you implement using QueryInterface or QueryService.
Like all COM applications, all of the Testing Agent's methods return an HRESULT in addition to the retval. To use the HRESULT return value constants and error codes defined by UFT One, include <UFT One Testing Extensibility SDK installation folder>\SDK\include\TestError.h.
For examples illustrating how to use the UFT One Testing Extensibility API methods, see the source files of the sample applications and their Testing Agents. These files are installed in the <UFT One Testing Extensibility installation folder>\Samples folder.
The Testing Agent for the Hours Report Sample is a C++ implementation of many of the UFT One features that Testing Extensibility can support. The Hours Report Sample files include a Readme file that explains how to run the sample, and test it using UFT One with and without the sample's Testing Agent.
The Testing Agent for the QuickID sample application is a C++ implementation of only the basic methods of Testing Extensibility. The QuickID files include a Readme file that explains how to run the sample, and test it using UFT One with and without the sample's Testing Agent. The purpose of the QuickID sample is to demonstrate how to get started when implementing a Testing Agent. Getting Started with UFT One Testing Extensibility walks you through the stages of developing the Testing Agent for this application.
The Testing Agent for the Maps sample application demonstrates creation of an agent in C#. The Maps sample files include a Readme file that lists the prerequisites that you need for this sample and explains how to run the sample and test it using UFT One with and without the sample's Testing Agent.
These sample Testing Agents do not provide support for creating text or text area checkpoints or output values on the sample applications.
With tests created using the Hours Report Sample and the QuickID sample, UFT One cannot recognize objects if a regular expression is used for a property value.