29 september 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.17. 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
- Design teststeps much quicker!
- Reuse definitions for change, retrieve and delete teststeps, based on existing teststeps
- Teststeps for associated objects are also automatically created
- Create teststeps to fill microflow parameters on the fly!
- Drag and drop teststeps!
- Use drag&drop to position teststeps or move them to another test case
- View and fix resulting constrution errors realtime
- Use real data when designing teststeps!
- Build create or retrieve teststeps based on actual objects in the database
- The object's attributes and associations are used in the teststep
- Design-time select which database to use
- Feeling lucky? Use the single-click microflow test button and MTA will randomly insert values for all attributes!
Make sure to download the latest MTA Plugin Module version before using this version of MTA.
|New functionality||It is now possible to fill attributes with user-selected values from the database on a Create or Retrieve object teststep.|
|New functionality||It is now possible to randomly fill attributes with values from the database on a Create or Retrieve object teststep.|
|New functionality||It is now possible to create a Retrieve, Change or Delete teststep, using the output of an existing teststep, using the menu under the "..." button on that teststep.|
|New functionality||If an MTA user logs in without having an API key or Personal Access Token (PAT) filled in, a popup window will show allowing the user to enter this information.|
|New functionality||When adding a new Create Object teststep, all attributes are now unselected by default (this was already the case for Change Object teststeps).|
|New functionality||It is now possible to use drag and drop to reorder teststeps in a test case, in a separate Edit page. The option for deleting and renaming teststeps has also moved to this page. Resulting construction errors are shown in realtime, but the operation can now be made undone to prevent these errors from happening.|
|New functionality||When selecting an entity from the domain model while adding a Create/Change/Retrieve/Delete object teststep, the name of the teststep is now auto generated and the popup window to enter the name is skipped.|
|New functionality||When selecting a microflow while adding a Microflow teststep, the name of the teststep is now auto generated and the popup window to enter the name is skipped.|
|New functionality||It is now possible to test a Mendix project where Git is selected for the source control. The result of this is that Application Branches are no longer part of MTA.|
|New functionality||When executing a Ci/Cd Test Run using the MTA Ci/Cd API, and MTA detects that the application commit (revision) number of the Test Configuration does not match that of the Application Environment, MTA will download the new application commit asynchronously, so that the API consumer will get a result immediately and not have to wait or handle a time-out.|
|New functionality||If a Ci/Cd API call yields an error message, this error message is now formatted as a JSON string.|
|New functionality||Creating a teststep is now done from the menu under the + Teststep button instead of choosing the teststep type in a popup window.|
|New functionality||Moving a teststep up and down is now done from the menu under the "..." button on the teststep. Note that moving the top teststep Up, will make it move all the way down, and moving the bottom teststep Down, will make it move all the way up!|
|New functionality||Moving a teststep to another Test Case can now be done from the menu under the "..." button on the teststep.|
|New functionality||When a construction error is shown due to a microflow being deleted, the name of the microflow is now included in the error.|
|Problem||The max range of a saved date time assert is not saved correctly leading to errors.|
|Solution||Saving an assert on a date time attribute now works as expected.|
|Problem||Only the first 100 attributes of an object were shown in a Create/Change/Retrieve object teststep.|
|Solution||All attributes are now shown in a Create/Change/Retrieve object teststep.|
|Problem||When recording a list view with a reference selector, MTA is not able to determine which entity to retrieve for the input change object.|
|Solution||Recording a list view with a reference selector now works as expected.|
|Problem||The Copy Test Suite popup only shows the first 10 target Test Configurations.|
|Solution||All target Test Configurations are now shown in the Copy Test Suite popup.|
|Problem||When trying to update a revision but the MTA user associated Mendix user does not have access to the Mendix App, the user will get the message that their credentials are not valid.|
|Solution||When trying to update a revision but the MTA user associated Mendix user does not have access to the Mendix App, the user will get an appropriate error message.|
|Problem||Chromium browsers consistenly ignore the Do Not Autocomplete setting in Mendix, leading to MTA usernames and passwords showing in the respective associated Mendix username and API key fields.|
|Solution||When entering the associated Mendix username and API key, an extra action needs to be performed to show these fields, preventing Chromium browsers from autofilling them with incorrect values.|