Extending proxies

Functional Tester 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 Functional Tester architecture enables developers to write a proxy for a particular UI control. Developers can enable Functional Tester to process the specifics of a control by writing proxies. Relevant functional testing capabilities can also be provided.

Proxies provide Functional Tester with details about a control for which it is written. Functional Tester 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, Functional Tester 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 Functional Tester can also be changed by creating new proxies.

Related concepts

Understanding proxies

Proxy development environment

Current level of proxy support that Functional Tester provides

Developing proxies using the Proxy SDK wizard

Related tasks

Set up proxy projects