Mendix 5 uses CSS classes to identify page content like widgets and popups. You can use these classes in Selenium to manipulate pages and verify data.
1. Naming conventions
Widgets can be given a name in the Mendix modeler. These names appear in the HTML document as class names prefixed by ‘
mx-name-’. For instance, a grid named
ArtistGrid will get a CSS class ‘
mx-name-ArtistGrid’. This is true for all widgets.
More complex widgets, like a grid, can set more specific CSS classes to sub-elements like columns or the paging bar buttons.
Some widgets, like a Grid or a Listview, can show multiple items. Every item has a CSS class ‘
mx-name-index-’ followed by an index number, starting at 0.
The easiest way to discover these names is to use a browser’s developer tool, like Firebug.
2.1 Nested widgets
Every widget has a unique class name, which means that you can use the name on its own as a selector in Selenium. This makes hem robust against changes in your page, like moving a button from one container to another. However, not all sub-elements in widgets are unique, like the buttons in the Grid’s paging bar. To select such an element, use a descendant selector like ‘
.mx-name-artist-grid .mx-name-next’. This first selects the artist grid and then searches for the next page button on that grid.
2.2 Timing issues
Some actions done by Selenium take time to complete, for instance animations or requesting data for a pop-up. When clicking a search button in a grid, the search bar appears using an animation. This means that after clicking the button, the test needs to wait for the animation to complete, before continuing.
For more information, see the Webdriver: advanced usage page.
Select a Microflow button named
Execute in a page:
Select the fourth row a grid named
Note that the fourth row in a grid has an index of 3.