Release 2.9
Release date
8 November 2024
Supported Mendix versions
Menditect supports the Mendix Long-Term Support Version (LTS) and Medium-Term Support Version (MTS).
Read more about MTS/LTS versions at Mendix docs: https://docs.mendix.com/releasenotes/studio-pro/lts-mts.
For support levels on MTS/LTS and monthly releases, read the SLA.
Highlights in this release
Download revisions automatically! Reduce waiting time with Branch Subscriptions.
Execute a single variation in the data variation. Re-testing failed test variations is now much faster.
New functionality
| ID | MTA-1453 |
|---|
| New functionality | It is now possible to subscribe to a branch. Subscribing will always download the latest revision in the background, automatically. The polling rate can be set to high, medium or low. |
| Release actions | None. |
| ID | MTA-1907 |
|---|
| New functionality | It is now possible to execute a single variation in Test Suite Datavariation page and Test Case Datavariation popup. |
| Release actions | None. |
| ID | MTA-1948 |
|---|
| New functionality | The MTA Public API can now be used to check if a Test Configuration, Test Suite or Test Case contains a Construction Error. This property can be used to check if a Test Configuration can be adapted; or after an adapt, to check if a Test Configuration can be executed. |
| Release actions | None. |
Bug fixes
| ID | MTA-1962 |
|---|
| Problem | Revisions downloaded using the MTA Public API, in a Git branch other than main, were visible but unusable in MTA. |
| Solution | Any revisions downloaded using the MTA API can be used to adapt Test Configurations to. |
| Release actions | Affected revisions will be repaired in the migration that starts after startup of MTA. |
| ID | MTA-1969 |
|---|
| Problem | If a Test Configuration was still adapting while Snapshots were being cleaned up, the Snapshot was deleted. This resulted in being unable to restore a Test Configuration after an adapt failed. |
| Solution | Snapshots won't be cleaned up if the associated Test Configuration is still being adapted. |
| Release actions | None. |
| ID | MTA-1927 |
|---|
| Problem | Adding a Persist teststep in an empty Test Case resulted in an error. |
| Solution | Adding a Persist teststep in an empty Test Case no longer results in an error. |
| Release actions | None. |
| ID | MTA-1940 |
|---|
| Problem | Cancelled Test Runs that are used in a Coverage Calculations on Application level cannot be deleted. |
| Solution | Cancelled Test Runs that are used in a Coverage Calculations on Application level can be deleted. |
| Release actions | None. |
| ID | MTA-1957 |
|---|
| Problem | Known issue from MTA 2.8.0: it was not possible to Copy a Test Suite if there was a Teststep that contained values filled with the output from a previous Teststep. |
| Solution | It is again possible to Copy a Test Suite if there is a Teststep that contains values filled with the output from a previous Teststep. |
| Release actions | None. |
| ID | MTA-1904 |
|---|
| Problem | In some cases, deleting a teststep (or Test Case / Test Suite with teststeps) had to be done twice for the object to be actually deleted. |
| Solution | It is now only necessary to perform deleting a teststep once. |
| Release actions | None. |
| ID | N/A |
|---|
| Problem | If MTA was stopped while a revision was being downloaded, the download status was still "Downloading" after MTA was restarted. |
| Solution | If MTA is stopped while a revision is being downloaded, the download status is now changed to "Error", allowing the Tester to retry the download. |
| Release actions | None. |