Selecting the Custom Server Run-Time Context Depending on the Test Function

Each Custom Server may implement the following test functions for each control:

Run-time contexts include:

The following table provides guidelines for determining which test function you can implement for each run-time context.

Need / Task

Test Record

Test Run

Table Verification

Run-Time Context

Explanation

Create tasks using keyword-driven testing (and not by recording steps on an application)

Not applicable

Yes

Only for .NET DLL Custom Servers

Either Application under test or UFT

The Test Record test function records the actions performed on the application being tested and the application's resulting behaviors. The recording is then converted to a test. If you plan to create GUI tests using keyword-driven testing, and not by recording steps on an application, you do not need to implement the Test Record function.

Implement the Custom Server in the Application under test context

Optional

Optional (usually)

Only for .NET DLL Custom Servers

Application under test

The Test Run function tests if the application is performing as required by running the test and tracking the results. Test Run is nearly always implemented in the Application under test context.

Listen to Microsoft Windows messages

Yes

Only with assistant classes

Only for .NET DLL Custom Servers

UFT

If the .NET DLL Custom Server must both listen to Windows messages and access control events and properties, use assistant classes. The Custom Server running in the UFT context can listen to events in the Application under test context with assistant class objects that run in the Application under test context. These objects also provide direct access to control properties.

Implement table checkpoints and output values on custom grid controls

Optional

Optional

Only for .NET DLL Custom Servers

Either Application under test or UFT

You can implement support for table checkpoints and output values on custom grid controls, regardless of the context in which your .NET DLL runs.

Your application uses UFT services more than it uses services of the custom control

Yes, but possibly less efficient

Possibly more efficient

Possibly more efficient

UFT is preferred

There is no need to listen to Windows messages during a Test Run session, so the UFT context is not required. However, if your application uses UFT services more than it uses services of the custom control, it may be more efficient to implement Test Run in the UFT context.