Glossary

Application: Any web or desktop application with visual controls that the user can interact using the mouse and keyboard.

Control Factory: delegates a Control Implementation corresponds to each Control Interface.

Control Implementations: are the logic for executing interactions with the application controls.

Control Interfaces: are public interfaces that define the interactions that each control has.

Control mapper: Is a component that takes a recorded control and gets the Control Interface related to it.

FlaUI: UI Automation technology is used to interact with desktop applications. For more information about FlaUI click here.

Interactions: User inputs on controls like Click or Sendkey.

Monitor: Component that handles user interaction recordings and UI Tree retrieval. Can exists on multiple technologies.

Page Objects: Are class containers for the Control Interfaces. Usually, it corresponds to a window in a desktop application or a page in a web application. Learn more about it.

Page Service: takes the Page Object and initializes all its controls with the corresponding Control Implementations.

Recorder Model: Structure that contains a set of controls and the interactions performed on them.

Selenium: Selenium's WebDriver technology is used to interact with web applications. For more information about Selenium click here.

Test Cases: Uses the Control Interfaces defined within the Page Objects to interact with the application under test.

Test Generator: Creates an UI Player script based on a Recorder Model.

UI Tree: An structure of controls and its ancestors, usually in form of a tree.

WebDriver: drives a browser natively, as a user would, either locally or on a remote machine.