| These release notes are from a version that is no longer used. |
14 july 2022
Supported Mendix versions
Menditect supports the Mendix Long-Term Support Version (LTS) and Medium-Term Support Version (MTS). The current highest monthly release that can be downloaded is 9.15. For support levels on MTS/LTS and monthly releases, read the SLA.
Read more about MTS/LTS versions at https://docs.mendix.com/releasenotes/studio-pro/lts-mts.
Highlights in this release
Bring MTA to your workplace!
- You can now buy an MTA "bring your own cloud" license.
- Keep your data safe on your own private or public cloud.
- Or, just install it on-premise.
- Contact email@example.com for more information.
Run a single Test Case!
- Execute a Unit Test with one click.
- No longer needed to isolate a Test Case.
Rollback transactions in a Test Case!
- All the data committed and deleted in both Object and Microflow teststeps is undone.
- No need to delete data created in your Unit Test anymore.
- Dependencies with other Test Cases are automatically checked.
Make sure to download the latest MTA Plugin Module version
before using this version of MTA.
|New functionality||It is now possible to buy an MTA "bring your own cloud" license and implement MTA on your own environment. Additionally, MTA will now also work if the database is implemented on Microsoft SQL Server.|
|New functionality||It is now possible to rollback all database transactions performed in a single Test Case. |
This includes all commits that have been done in microflows.
|New functionality||It is now possible to execute a single Test Case as long as it does not use any data from previous Test Cases.|
|New functionality||MTA now contains context sensitive help buttons that guide you directly to the related page in the Reference Guide.|
|New functionality||Several improvements were made in the Recorder functionality.|
|New functionality||Several improvements were made in the user interface. |
What are your top 10 user interface improvements? Let us know!
|New functionality||It is now possible to select a specialization of the entity when selecting an object for a microflow parameter.|
|New functionality||It is now possible to select 'empty' for an association in an object teststep.|
|New functionality||When executing a Test Configuration, only the Test Applications that are actually used in Test Cases in the Test Configuration, are checked for availablilty.|
|New functionality||When selecting a Date value and choosing to either enter a date or calculate the date based on the current date, the first option is now called "Specified date" instead of "Fixed date".|
|New functionality||Running into a validation error upon execution of a Test Case no longer leads to the Test Case Run result being Failed. |
We are also working on being able to assert on a validation error. This will be implemented in a future release!
|New functionality||If an attribute or assert is used in datavariation it is no longer possible to change the value from the Test Suite page, but only in the datavariation page.|
|Problem||When entering the Mendix username and API key on the My Account page sometimes the username was not saved correctly, due to Chromium browsers autofilling the field. This resulted in the MTA user not being able to download any Mendix models but also not being alerted about the fact that the username was not saved.|
|Solution||Alert the user when the username is not correctly filled in upon entering Mendix username and API key.|
|Release actions||Some MTA nodes currently have Mendix users where the username is unknown. A migration script will be executed on these MTA nodes where the username will be set to "user unknown". Please check the My Account page when not being able to download any Mendix models in MTA.|
|Problem||When enabling "Trim value" for assert on a String attribute the result would always be Passed if the attribute is of type "String unlimited".|
|Solution||"Trim value" for assert on a String attribute now works as expected.|
|Problem||When using a list of objects that is returned from a microflow teststep, an error would occur if the microflow returned 'empty' (instead of a list with 0 objects).|
|Solution||Using a list returned from a microflow no longer results in an error.|
|Problem||Test configurations not-executed were not correctly displayed on the Dashboard.|
|Solution||The Dashboard now displays Test Configurations executed and not-executed correctly.|
|Problem||In some cases it was not possible to delete an Application, even if all associated Test Configurations and Test Runs were deleted.|
|Solution||Applications can now be deleted when all associated data is deleted.|