MTA Plugin
Purpose
In order for MTA to communicate with the Application Instance under test, you need to import the MTA Plugin module created by Menditect that will initiate this communication.
Usage
The Installation Guide covers instructions on how to install and configure the MTA Plugin.
If a Test Run starts in MTA, the MTA Plugin triggers the execution in the Test Application, and returns the results of the test to MTA.
To determine whether a Microflow is triggered by MTA, call the Is_Current_Execution_By_MTA Rule in the MTA Plugin.
Supported Versions
| MTA Plugin 9/10/11 | MTA Plugin 4.8.1 | Any older MTA Plugin | |
|---|---|---|---|
| MTA 3.0 | Supported | Partial support * | Not supported |
| MTA 2.10 | Supported | Supported | Not supported |
| MTA 2.9 | Not supported | Not supported | Not supported |
* Teststep Exception handling and Test Run FileDocument downloads won't work.
Because Menditect now hosts all Mendix Runtime versions (9, 10 and 11) in the same marketplace component, we have moved to a different versioning system. The major MTA Plugin version indicates the Mendix Runtime version. The remaining digits indicate the internal version of the MTA Plugin.
Installation instructions
- Import the MTA Plugin Add-on module into your Application from the Mendix Marketplace.
- Follow the Installation guide to configure the module.
Update instructions
Updating from MTA Plugin 4.8.1
Delete the existing MTA Plugin from your Mendix project, delete MTA Plugin related JAR files from userlib, and delete the MTA Plugin directory from javasource in your project directory.
Updating from MTA Plugin 9 and above
- Import the MTA Plugin Add-on module into your Application from the Mendix Marketplace.
Feedback?
Missing anything? Let us know!
Last updated: 17 September 2025