Support MES Test Manager® (MTest)

What is MTest?

The MES Test Manager® (MTest) is a model test manager that supports the model tester in testing models and administering tests. MTest enables testing of Simulink®, Stateflow®, TargetLink®, and Embedded Coder® models.
MTest carries out the often-repetitive tasks that make up the testing process: from analysis of the models to be tested, to test frame creation, the testing execution itself, and test documentation. The tool also provides the tester with valuable support in the test planning and test specification stages.

Highlights in MES Test Manager® (MTest) v.7.4

Test sequences are generated automatically from MARS requirements in batch mode.

Model coverage filters that are applied can now be justified in documented annotations. .


MTest v.7.3

Highlights in MES Test Manager® (MTest) v.7.3

The Simulink Coverage Toolbox is now supported measuring code coverage during testing of Embedded Coder® models.
Available for MATLAB 2018b or newer.

Assessments derived from MARS requirements can be automatically created during batch testing.

MTest v.7.2

Highlights in MES Test Manager® (MTest) v.7.2

ReqIF export of MARS requirements. You can now comfortably export formalized requirements created with MARS to the *.reqif file format. This export file is created automatically when saving the *.mars file in the MTest Specification Editor.

Testbed generation now supports resolving of referenced subsystems. With this release we support referenced subsystems (as introduced in R2019b). While generating a testbed referenced subsystems are handled in analogy to referenced models, i.e. they are converted to subsystems. Additionally, we now resolve all links to libraries and/or referenced models and subsystems by default. This helps you to ensure an invariant testbed for models that make use of references.

MTest v.7.1

What's New?

Highlights in MES Test Manager® (MTest) v.7.1

External requirements in reqif-format can be conveniently imported into your test project. Supported by graphical user interface, the import attributes can be adapted to the custom format of your requirements document, and additional filter rules, e.g. regarding the testability of requirements, can easily be applied.

The automated test case generation has been improved further and has been made more robust. Ranges of interface signals are read from the model directly, the resolution of signals is set automatically according to signal data type, and Boolean signals are handled fully automatically.

The extended project configuration
now includes the evaluation settings for central configuration and roll-out.

MTest v.7.0

Highlights in MES Test Manager® (MTest) v.7.0

New approach in Configuration Management
The test project configuration has become easier and more convenient, the configuration setup can also be saved and distributed, which enables standardized configurations within a team or organization.

MARS Requirements Included in Test Documentation

Change Impact Analysis on MARS Requirements

MTest v.6.4

Highlights in MES Test Manager® (MTest) v.6.4

Automated generation of functional test cases based on MARS requirements (ALPHA)
For given types of MARS requirements, MTest can now automatically generate test sequences (incl. test vectors) that will trigger the software behavior as defined by the MARS requirement.

Please kindly note, this feature has ALPHA status, and we highly encourage our customers to provide us with their feedback and ideas about it.

Redesigned test project protocol
Test object-specific issues can be identified individually and more quickly with help of the redesigned test project protocol.

MTest v.6.3

Highlights in MES Test Manager® (MTest) v.6.3

Test case generation by variation:
A logical test case in MTCD can include any number of variation points, that are defined by a list of values or parameters. A combination algorithm then creates test sequences automatically.

Extended support of logged signals in signal comparison evaluation

Support of the Simulink Data Dictionary in combination with referenced models



  • If you receive MTest in one zip file, please extract it into a folder. Please keep all the subdirectories.
  • Suggestions:
    • C:\Program Files\mtest
    • x:\project\matlab\mtest
    • <MATLAB_ROOT>\toolbox\mtest
  • (Optional) Include the ...\mtest\bin directory into your MATLAB® path (only the \bin directory, all path setting is handled by MTest).
  • See also Chapter 2 of the User Guide.

If you want to run MTest and MXAM concurrently, run MTest's and MXAM's path initialization before running MTest and MXAM:

  • Copy the MTest_MXAM_SideBySide.m script from the demo folder of your MTest installation. For example into your MATLAB® startup folder.
  • Change the values of the ``mxamRoot`` and ``mtestRoot`` variables to your MTest and MXAM installation locations.
  • Execute the script manually or let MATLAB® execute it on each start.
  • You may now start MTest and MXAM in any succession.
  • See also Chapter 2 of the User Guide.


Update to the Latest Version

  • You should keep a backup of your old MTest installation (just rename the MTest directory to MTest_x using the "old" version number)
  • Then proceed according to the installation instruction given above. If you use the previous MTest directory, you do not have to include the mtest\bin directory in your MATLAB® path again.
  • After installation you reuse all your project settings directly (they are not part of the program installation).
  • When using a floating license and changing to a new major release (from MTest 5.x to 6.x), please copy your license configuration to the new major-version-specific MTest lismo directory (see MTest client configuration above; use subdir 6_0 instead of 5_0).

System Requirements

The following system requirements must be in place to use MTest:

  • Matlab® R2011b to R2020b
  • Targetlink® (base suite) v3.X to v5.0
  • Windows® 7, 32-bit and 64-bit versions or Windows® 10 (for running MATLAB®)
  • System requirements when using MTest with EXCEL: Microsoft® Excel® 2003 and higher
  • Please note: When working with Testwell CTC++, Microsoft® Visual Studio® or Microsoft® Windows® SDK is a prerequisite. The user must have write access to the compiler installation folder.
  • System requirements when using MTest with CTE/TESTONA: CTE 3.x or TESTONA 4.x/5.x+

Quick Start

  • Open MATLAB®, navigate to the MTest installation directory and execute >> mtest
  • During the first start up, MTest asks for your project preferences (name, short name, model directory, test directory, ...)
  • See also Chapter 2 of the User Guide


If you have any suggestions to help us improve the MES Test Manager® (MTest), please do not hesitate to contact us:

User Instruction

MTest User Guide

User Guide

The MES User Guide presents clear instructions on how to work with the MES Test Manager® (MTest). It provides users with information about getting started and working with MTest.
You can easily call the User Guide by clicking on "Help" > "View User Guide" (see image).

MTest Videos

In this video we will demonstrate how to use the new test case variation feature by means of a specific example, namely how to define a logical test case from which concrete test cases can be derived. You will need to have basic knowledge about MTest and the MTCD test description method to watch this video.

Release Notes - MTest v.7.4 (March 2021)

  • Batch Regeneration of Test Sequences from MARS Requirements
      Similar to the batch regeneration of assessments the user is now able to regenerate test sequences from MARS requirements within the batch test. For this purpose, the new option 'Regenerate & Import Test Sequences' is available within the Batch Test GUI.
      Please note: During batch re-generation of already existing generated test groups, the corresponding MTCD files (*.mtcd) are backed up in the corresponding test object directory of the editor workspace (i.e. /editorWorkspace/...
  • User Rationales for Model Coverage Filtering (#8838)
      Within the Coverage Filter Configuration, the user can now provide their own comments to justify the ignoring of the selected subsystem. These annotations are also included in the corresponding Simulink Coverage Report. For this purpose, the field 'Rationale' has been added to the structure containing the ignore list. Please refer to the example below:
        CovFilterConfig.IgnoreList = [ ...
        struct('Path', '<SUBSYSTEM_A/' ...
          ,'SID' , ''...
          ,'Rationale' , 'This is excluded because of ...'...
          ); ...
      Please note: This type of exclusion is only available for the model coverage. If your use case calls for both model and code coverage you are strongly advised to only ignore subsystems.
      If block instances - other than subsystems - are ignored you are advised to disable the code coverage filters by setting your configuration parameters 'TLCodeCoverageFilterEnabled' and 'CTCCodeCoverageFilterEnabled' to 0, respectively.
  • Enumeration Members Available for Use in MTCD (#6417, #7875, #8609, #8611)
      With this release, enumerations can be used within MTCD test descriptions. For this purpose, the required enumerations and their members must be declared in the interface file. Here is an example:
        enum Color {
      Please note: The declaration of the enumerations in the corresponding *.io file must be done by hand for now. Automatic retrieval of the enumerations used by the test object will be part of later releases of MTest.
  • New Option for Handling Input Data Type Conversion within the Test Bed
      We introduced a new configuration option which controls the settings of the data type conversion blocks in the generated testbed.
      For this purpose the parameter InheritInputDataTypes is introduced. It can hold the following values:
        0: Inactive. (Input data type conversion is set to the data type according to interface analysis)
        1: Active. (Input data type conversion is set to 'Inherit: Inherit via back propagation'.
        The default value is 0.
      Please note: While this option is active it may lead to signals with under-specified data types - depending on the test object. In this case Simulink will display specific warnings.
  • Discontinued Support for MATLAB R2011b to R2013a
      This release officially removes support for MATLAB R2013a to version R2011b. From now on, MTest officially supports MATLAB R2013b-R2020b.
  • Further Bug Fixes
      #8920: This fix ensures that the testbed is compilable during its generation. In the past, this could lead to errors with TargetLink test objects that required a rescan of the buses.
      #8928: With this fix the access to parameters of type Simulink.Parameter in MARS has been simplified. These can now be queried directly, i.e. access via MySimulinkParameter.Value is no longer necessary.
      #8943: This change has made the documentation of the project or test authors more consistent. The catalogs now uniformly list the project author in their respective headers, while the headers of the test reports, on the other hand, show the respective test authors.