Release 2.7.0
Release date
15 July 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.
Watch the video on Code Coverage!
Highlights in this release
Introducing Code Coverage. Know which microflows are covered by your tests! Define specific coverage goals and measure coverage trends.Improved analysis of Test Runs by providing links to Teststeps that use a specific output.
Added instructional Demo Video's to MTA.
Added the option to execute with a Teststep delay, which allows more fine-grained waiting than Test Case delay.
Optimized Test Run performance by providing the choice for normal (faster) and full output.
New functionality
| ID | MTA-1401 |
|---|---|
| New functionality | Added the option to measure the Code Coverage of microflows that were executed in Test Runs. Look for the icon! This will be measured after a test was executed, on both Test Configuration and Application level. A 100 % coverage means all microflows were executed. Set Coverage Goals with Exclude Filters to exclude microflows. Use the Coverage Goals navigation item on your Application or Test Configuration to get started. |
| Release actions | Test management apps using MTA's Public API to execute a Test Configuration, have to provide a "Coverage" parameter in the body. Check the reference guide for more information. |
| ID | MTA-1333 |
|---|---|
| New functionality | Added the Delay option on a teststep, to specify how long MTA should wait before executing the next teststep. If a delay other than 0 was specified, the delay is shown in the teststep. Look for the icon! |
| Release actions | None. |
| ID | MTA-1752 |
|---|---|
| New functionality | When executing any test, a choice must now be made to run the test with "Full output" or not. Look for the icon! Running without full output, which is now the new default setting, will be faster than before, but when viewing the results of the Test Run, teststep values are only shown if they are used by other teststeps. Running with full output will include all data values when viewing the results of the Test Run. |
| Release actions | None. |
| ID | N/A |
|---|---|
| New functionality | When executing any test, it is now possible to navigate through the output values of teststeps to determine in which other teststeps that output is used. Because there was already an option to see which teststep is providing input, these values are now fully navigable, back and forth. |
| Release actions | None. |
| ID | N/A |
|---|---|
| New functionality | Added instructional demo video's to MTA. Just click on the button in the top-right in MTA. |
| Release actions | None. |
Bug fixes
| ID | MTA-1727 |
|---|---|
| Problem | Specifying a single quote (') as value of a String attribute in a retrieve teststep would lead to incorrect escaping when executing the test. This is because single quotes are escaped differently in XPATH parameters. |
| Solution | Single quotes are now escaped correctly, resulting in correct XPATH parameters. |
| Release actions | None. |
| ID | MTA-1822 |
|---|---|
| Problem | Unlimited String values could not be copied from attributes in the results of a Test Run. |
| Solution | Unlimited String values can now be copied with a Copy button from attributes results of a Test Run. |
| Release actions | None. |
| ID | MTA-1835 |
|---|---|
| Problem | Microflow teststeps with the same output data type as needed for an input parameter are not visible (and cannot be used as input) if those microflow teststeps have input parameters where datavariation is applied. |
| Solution | Microflow teststeps with the same output data type as needed for an input parameter are visible so they can be used as input. |
| Release actions | None. |