Frontend test guide
This guide describes step-by-step how to prepare for, design, and run a Frontend test in MTA and analyze the run results.
Prepare
Add Class
Start by adding a Class to each Mendix Page you want to test.
Import modules
Then, download and install the Connector and Testkit modules, required for Frontend testing.
Download Pages and Widgets
Enable the downloading of Pages and Widgets on the App you want to test.
Download a new revision and adapt the Test Configuration, so Page and Widget information is loaded into MTA.
Design
Setup the Test Cases for the Frontend test.
Generate the Teststeps for the Frontend test.
Enable Tracing for the Frontend Test so you can re-watch the browser in action.
Run
Run the Frontend test
Run the test and analyse results with the Trace file
When a Frontend test is executed with one of the Menditect Playwright Modules, a Browser will execute the commands. Depending on how the Browser is hosted, and if you've chosen to run a Headless test the Browser window will also be visible during the test. It may take some time for Playwright to load it's libraries into memory and for the Browser to to become visible.
If the Test Run stalls in MTA and it takes too long for the Browser to become visible, it may be necessary to restart your computer.
Analyzing a Frontend test
The results of a Frontend test can be stored in a Playwright Tracefile.
If a Frontend test fails with a Teststep Exception, the Playwright Tracefile may not be generated, because the Teststep that stores the Tracefile was not executed.
To make sure that this Teststep will be executed, set the Exception Handling property to Continue on the preceding Teststeps.
Feedback?
Missing anything? Let us know!
Last updated 18 March 2026