|Introduction to Action Based Testing / ACTION BASED TESTING|
An automated test execution needs to interact with the application under test through one or more interfaces.
In most cases the interaction is with user-oriented interfaces, like dialog boxes or web pages. In many cases, though, part of the test, or even the entire test, must interact with the AUT through other means, such as messages, API calls or SQL statements. In Action Based Testing, all interface interaction is be supported through the use of interface definitions.
An interface is usually related to a platform, such as Java, .Net or Web. An interface entity is typically specific to a screen or a web page. An interface element is usually a control or HTML element.
In the non-UI interfaces, interface definitions can also be applied. For a message protocol, an interface entities can depict a message, while the interface element can describe a message field.
The interface definition in essence assigns a logical name for a physical interface item. Properties of the interface item, like the title of a window or the caption of a button, serve to allow the automation to map the logical name to the actual item during test execution. For example, a dialog box with a title of Application Error might be given the logical name error message. The title, in this case, is the property used to identify the item.