Share this page
Developing support for a Custom WPF Toolkit (Version 2022 or later)
Relevant for version 2022 or later
This topic explains when to use extensibility and create custom support for version 2022 or later. For version 2021 R1 or earlier, see Developing Support for a Custom WPF/Silverlight Toolkit (Version 2021 or earlier).
OpenText Functional Testing 2022 and later: Following the discontinuance of the Silverlight development framework, OpenText Functional Testing no longer supports the Silverlight Add-in by default.
If you need to use and extend the Silverlight Add-in, contact OpenText Support.
Many WPF (Windows Presentation Foundation) customer applications include use of non-Microsoft controls in their UI. OpenText Functional Testing represents these controls with the generic WpfObject test object.
In other cases, OpenText Functional Testing recognizes a complex control as a set of low-level controls, instead of recognizing the functional significance of the high-level control. For example, OpenText Functional Testing might recognize a custom WPF calendar control as several unrelated buttons and text boxes.
In these cases, the tester cannot run any methods containing logic specific to the custom control type. Nor can the tester apply any recording logic specific to this control type.
By creating a toolkit support set using WPF Add-in Extensibility, you define new test object classes to represent these custom controls. The support set gives QA engineers the ability to run, record, learn and spy on custom WPF controls.
This section includes:
