Marketplace release v10.0.4

• We fixed an issue where renaming or deleting a module resulted in the test suite overview showing incorrect data.

Marketplace release v9.6.3

• We fixed an issue where renaming or deleting a module resulted in the test suite overview showing incorrect data.

Marketplace release v10.0.3

• We updated the commons-lang3 dependency to 3.18.0

Marketplace release v9.6.2

• We updated the commons-lang3 dependency to 3.18.0

Marketplace release v10.0.2

• We included the OSS clearance report and license file in the module package.

Marketplace release v10.0.1

• 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.

Marketplace release v9.6.1

• 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.

Marketplace release v10.0.0

• 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

Marketplace release v9.6.0

• We upgraded the module to Mendix version 9.24.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

Marketplace release v9.5.2

• We updated the Apache Commons IO dependency to 2.17.0