All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- We migrated from SASS to CSS variables to ensure compatibility with Atlas 4.
- We increased the length of the ‘Name’ and ‘DisplayName’ attributes in the UnitTest entity, the ‘Module’ attribute in the TestSuite entity, and the ‘TestName’ attribute in the UnitTestContext entity to align with the maximum allowed lengths for module and microflow names in the platform. (#259822)
- We fixed an issue where renaming or deleting a module resulted in the test suite overview showing incorrect data.
- We updated the commons-lang3 dependency to 3.18.0
- We included the OSS clearance report and license file in the module package.
- We fixed an issue that caused unit test microflows with auto-committed objects to fail with an unhandled exception (#244962, #246277, #246384).
- We fixed reporting issue for ThrowAssetionFailed action. Now a failed unnamed assertion step will be reported.
- We upgraded the module to Mendix version 10.21.0 for compatibility with Mendix 11
- We updated Atlas Core compatibility to version 3.17.0
- We updated Atlas Web Content compatibility to version 3.8.0
- We updated Data Widgets compatibility to version 2.31.0
- We introduced a modernized and responsive UI for the unit test overview page.
- We added filters to enable filtering based on test results.
- We introduced a test execution timeline. You can view all the activities in the order that they were executed in. Activities include start, reported steps, assertions, exceptions and end result.
- We now automatically discover added/removed unit tests. It is no longer required to reset/refresh the unit test overview.
- We now support evaluation of multiple assertions in the same unit test. Optionally, the unit test microflow execution will continue so you can still verify the result of other assertions. Note that a failed assertion will always result in a failed test.
- We now disable the unit testing module by default for any other environment other than local development. If you want to run unit tests in a deployed environment, set the UnitTesting.Enabled constant to true. We recommend to keep this constant set to false for production environments.
- We exposed a new microflow activity “Assert using expression“ in the microflow toolbox. This action can be used to add a name to your assertion and configure whether or not to stop on failure.
- We exposed the “Report step“ activity in the microflow toolbox. Use this action to track key steps of the test execution.
- We introduced a new optional unit test parameter “UnitTestContext”. During test execution, a UnitTestContext object will be passed to this parameter. You can use this object to get access to the name of the test and any assertion results. This can be useful when you have multiple assertions in a single test and want to use the outcome of previous assertions in your test logic.
- We added Accordion widget as a dependency, compatible with v2.3.4
- We updated Atlas Core module compatibility to v3.12.5
- We added Atlas Web Content module as a dependency, compatible with v3.4.2
- We added Data Widgets module as a dependency, compatible with v2.27.3
- We updated the Apache Commons IO dependency to 2.17.0
- We fixed the missing Dutch translations in the unit test details page
- We fixed log node name for the assertion error check microflow
- We updated the unit test details page for React client compatibility, introduced in Mendix 10.7.0
- We fixed an issue where the result of a test suite was not updated after running an individual test
- We fixed an issue in transaction handling for teardown microflows that could result in a database lock
- We changed the length to limited for the 'Name' attribute in the UnitTest entity
- We updated slf4j-api from 1.7.36 to 2.0.9
Note: Review the dependencies in the userlib folder after upgrading the Unit Testing module. Also, if you use any slf4j libraries other than slf4j-api, make sure their major versions are matching.
- We updated httpclient5 from 5.0.3 to 5.2.1
- We updated httpcore5 from 5.0.2 to 5.2
- We updated httpcore5-h2 from 5.0.2 to 5.2
- We updated slf4j-api from 1.7.25 to 1.7.36
- We removed the dependency on commons-codec-1.13
Note: Review the dependencies in the userlib folder after upgrading the Unit Testing module.
- We upgraded the module to Mendix version 9.18.0 for compatibility with Mendix 10
- We replaced the usage of “IContext.rollbackTransAction” with “IContext.rollbackTransaction”
- We upgraded the module to Mendix version 9.18.0 for compatibility with Mendix 10
- We replaced the usage of “IContext.rollbackTransAction” with “IContext.rollbackTransaction”
- We removed the dependency on the Community Commons module
- We updated the commons-lang3 dependency from 3.11 to 3.12.0
- We fixed an issue for JUnit-based unit tests, where a single unit test could be discovered and added to multiple modules in certain scenarios
Notes when upgrading from an earlier version:
- Review the dependencies in the userlib folder after upgrading the Unit Testing module. Remove the files 'commons-lang3-3.11.jar' and 'commons-lang3-3.11.jar.UnitTesting.RequiredLib', since commons-lang3 is updated to 3.12.0
- When upgrading from v9.1.0: If the Community Commons module is no longer used by any other module after the upgrade, you should remove the Community Commons module from your project. Review all dependencies in the userlib folder afterwards, and remove the dependencies that were required for Community Commons only
- When upgrading from v9.0.5 or below: If the Object Handling module is no longer used by any other module after the upgrade, you should remove the Object Handling module from your project. In this case, also delete the 'commons-lang3-3.7.jar' and 'commons-lang3-3.7.jar.ObjectHandling.RequiredLib' files from your userlib folder
-
We replaced the dependency on Object Handling module with Community Commons module Notes when upgrading from an earlier version:
-
The Community Commons module is now required for this module to work. Download the Community Commons module from the marketplace and review all dependencies in the userlib folder afterwards.
-
If the Object Handling module is no longer used by any other module after upgrading the Unit Testing module, you should remove the Object Handling module from your project. In this case, also delete the 'commons-lang3-3.7.jar' and 'commons-lang3-3.7.jar.ObjectHandling.RequiredLib' files from your userlib folder.
- We updated the commons-io dependency from 2.8.0 to 2.11.0 to be in line with Community Commons