For each known class of control, TestArchitect uses internal mapping files to map its native properties to a set of TA properties.
Just as it does with TA classes, TestArchitect defines a common set of properties for controls across all platforms. Mappings are established between the native properties of a given platform’s controls and the set of TA properties, based on each given control class and its platform.
A primary TA property is one that obtains its value directly from a given native property.
While most TA properties get their values directly from single native properties of their associated controls, there are some TA properties whose values are calculated, often from two or more native properties, or from other controls. We’ll examine a few examples.
TestArchitect scans application windows for their controls during both the identification and playback phases of testing, to establish the controls’ TA classes, TA properties and TA property values. This is called the intake process.