Extending proxies

HCL OneTest™ UI needs UI control-specific information to perform functional testing operations such as recording, playback, verification points, and data driving. It tries to map the closest proxy if it finds a new control for which it has no proxy.

The HCL OneTest™ UI architecture enables developers to write a proxy for a particular UI control. Developers can enable HCL OneTest™ UI to process the specifics of a control by writing proxies. Relevant functional testing capabilities can also be provided.

Proxies provide HCL OneTest™ UI with details about a control for which it is written. HCL OneTest™ UI has a predefined set of methods for any proxy and calls each method to get specific details. For any proxy written for a control, these predefined methods are implemented specific to the control.

For any control, HCL OneTest™ UI provides a set of properties and data types for verification. If the currently provided set of properties and data types is not enough to test the control, a new proxy can be created and by overriding certain methods more properties or data types can be included. The recording behavior of HCL OneTest™ UI can also be changed by creating new proxies.