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.

What's new?

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.

► Read about all new features in the Release Notes

System requirements

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

  • Matlab® R2011b to R2018b
  • Targetlink® (base suite) V3.X to V4.4
  • Windows® 7, 32-bit and 64-bit versions or Windows® 10 (for running MATLAB®)
  • System requirements when using MTest with EXCEL: Excel® 2003 and higher
  • Please note: When working with Testwell CTC++, Microsoft Visual Studio® 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+

Update to the latest version

  • You should keep a backup of your old MTest installation (simply rename the MTest directory to MTest_x using the "old" version number)
  • Then proceed according to the installation instructions given below. 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 can reuse all your project settings directly (they are not part of the program installation).
  • When using a floating license and changing from MTest 3.x to 4.x, please copy your license configuration to the new major-version-specific MTest lismo directory (see MTest client configuration above; use subdir 4_0 instead of 3_0).


  • If you receive MTest in one zip file, please extract it into a folder. Please keep all the subdirectories.
  • Suggestions:
    • D:\Programme\mtest
    • x:\project\matlab\mtest
    • %MATLAB_ROOT%\toolbox\mtest
  • Include the ...\mtest\bin directory into your MATLAB Path (only the \bin directory).
  • See also Chapter 2 of the User Guide

Quick start

  • Open MATLAB®, navigate to the MTest installation directory and execute >> mtm
  • 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 Guide

MTest 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).

Feature 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 6.4 (October 2019)

  • (Alpha) Functional Test Case Generation Based on MARS Requirements
      With the new release of MTest, we now provide a method for deriving test cases on the basis of formalized requirements created with the MTest Assessable Requirements Syntax (MARS). For given types of MARS requirements, the user is now able to automatically generate test cases (incl. test vectors) that will trigger the model behavior as specified by the requirement.
      This approach accelerates the creation of test cases. Moreover, the manual effort in composing a test suite is reduced, since both ends of testing - from simulation to evaluation - are now covered by MARS. Currently, this feature has alpha status which means that our users are highly encouraged to provide us with their feedback and ideas.
  • New Representation of the Test Project Protocol
      The representation of the Test Project Protocol - MTest's feature for checking the integrity of your test projects - has been completely restructured so that test object specific issues can be identified faster. For this purpose, the failed checks for correctness, completeness, consistency, as well as the suggestions for any follow-ups are listed for each test object individually. This aids navigating, checking, and counteracting issues you might encounter within your test projects.
  • Improved User Guide
      MTest's user guide is now available in HTML format allowing convenient use of document navigation and search (including search term highlighting), as well as bookmarking. A PDF print version of the user guide is still available as well, see '\doc\userguide\MTestUserGuide.pdf'
  • (Beta) Test Case Generation by Variation in MTCD
      The demo project - that can be set up automatically - now contains a sample test group (Autopilot_Mode_Logic\TestGroup003) that showcases the use of variation for deriving test sequences.
  • Test Object Selection
      When adding a test object to the test project, the user is now able to select the current system (as retrieved with GCS) as a new test object. This is a fast and convenient way to include a test object without potentially navigating extensive subsystem structures.
  • Evaluation Configuration
      The user can now specify whether manually created assessments and/or assessments generated with MARS should be considered for automatic test evaluation. This decouples both assessment types and eliminates the need to specify attributes for manual assessments, in case only MARS assessments were used.
  • Useful Links in Main Menu
      Quick access to useful websites is provided from the help section of the main GUI menu. Now, the user can directly open the following webpages: MES homepage, MES Webinar Series, and MTest Support.
  • Bug Fixes
      #7022: Fixed issues during testbed creation for test object utilizing bus objects and custom data types. This fixes a bug that occurred in MTest v6.2.1.
      #7108: Fixed issues with logged signals holding signal names that contain blanks, e.g. problems with *.io files and problems with tolerance configuration.
      #7147: Fixed issues with MTest batch project in the context of CI usage, where errors regarding the selection of TargetLink code coverage selection occured.This fixes a bug that occurred in MTest v6.2.1 and v6.3.
      NOTE: If you encountered this issue, updating your existing batch selection mat files is required. To do so, open the batch test GUI, select your desired batch actions, and simply save your selection.
      #7155: Fixed an issue with a confusing command window output when an entire test group was selected in the batch GUI, in conjunction with an active re-import option. In the past, a single sequence re-import was displayed even though it was skipped after successful re-import of the test group. This fixes a bug that occurred in MTest v5.0.
      #7168: Fixed an issue when analyzing the data type for a bus signal. In some instances, the data type was resolved to inherit instead of using the assigned bus object. This might lead to issues for data type conversions, when a specific data type is required. This fixes a bug that occurred in MTest v6.2.1.