Frontend Testing Glossary
Action
Context: Playwright
An Action can be done on an Element when it has been successfully located by a Locator. A Playwright Action simulates a user action like a mousebutton being clicked or a text being typed.
More info at: https://playwright.dev/java/docs/input
Assertion
Context: Playwright
An Assertion is a verification on an Element to check if certain claim about a property of that Element is true or not (properties described below). If an Assertion fails, the Playwright test also fails.
More info at: https://playwright.dev/java/docs/test-assertions
Element
Context: Playwright
An Element is a type of HTML (HyperText Markup Language) document component, one of several types of HTML nodes, on a single HTML webpage.
An Element can contain one or more nested Elements.
Technically an Element is defined by an opening and closing tag within the HTML source, for example <div> and </div>.
An Element can be visible on the Page.
Filter
Context: Playwright
A Filter is a specific kind of Locator; an attempt to narrow down a Locator that results in locating multiple Element, into locating a single Element.
More info at: https://playwright.dev/java/docs/locators#filtering-locators
Index
Context: Mendix
Index is a number that represents a position within a traversable collection. In Mendix the Index is used to indicate the position in a list, grid or other view that shows data from multiple database objects. Playwright uses zero-based indexing, meaning the first item in a collection is at Index 0.
Input
Context: Mendix
Only for Widgets that allow user interaction in order to save data. Input is the part of a Widget where user action is required to fill the Widget with a Value.
Label
Context: Mendix
Only for Widgets that allow user interaction in order to save data. Label is part of a Widget describing what kind of Input is required in the Widget. A Label on a Widget is optional.
Locator
Context: Playwright
A Locator is an attempt to describe (unique attributes of) a single Element allowing it to be located on the Page, in order to perform Actions on it. Locators allow for chaining meaning a nested Element further down the node tree can be located using a Locator of it's parent Element.
More info at: https://playwright.dev/java/docs/locators
Nth
Context: Playwright
Nth is a Filter using an Index to filter a Locator that results in multiple Elements, yielding a new Locator that only represents the Element on that Index. Playwright uses zero-based indexing, meaning the first item in a collection is at Index 0.
Playwright Page
Context: Playwright
A Tab page in the browser with an HTML source. There can only be one Page per browser Tab.
More info at: https://playwright.dev/java/docs/pages
Text
Context: Mendix
Any text that is visible on the Mendix Page and that can be used for a Filter.
Typically, Text is contained between an opening and closing HTML tag, for example <div> and </div>.
Tracefile
Context: Playwright
A .ZIP file that contains information about an executed Playwright Frontend test. The Tracefile is essentially a recording of all browser pages and elements during the test, and the Locators and Actions performed. The Tracefile Viewer in MTA can be used to view the recording.
More info at: https://playwright.dev/docs/trace-viewer#opening-the-trace
Value
Context: Mendix
The literal data, like a string, integer or date, being the result of Input. The Value does not have to be visible on the Mendix Page. Values can be stored to the database of the Mendix Application.
Widget
Context: Mendix
A Widget is a reusable, self-contained user interface element on a Mendix Page. It provides an interface that results in a corresponding HTML Element (with possible child Elements) when the Widget code is compiled and executed.
Related topics
Feedback?
Missing anything? Let us know!
Last updated 27 November 2025