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 latest versions of MES Test Manager® (MTest) v.7.6
- Interface analysis automatically updates the MARS/MTCD interface files *.io in order to ensure the correct up-to-date data is used during batch runs. The interface analysis now supports TargetLink bus vectors. Enumerations can manually be edited in the interface file.
- MTest report documents the application of coverage filters.
Highlights in MES Test Manager® (MTest) v.7.5
Enumerations in the MTest Specification Editor
Interface signals and workspace parameters of a test object that are of type “enumeration” will be automatically added to the *_interface.io file for use in the MTest Specification Editor.
Complex Signals in the Assessment Analyzer
The real and the imaginary part of complex mathematical signals are displayed separately.
General improvements in Robustness
Consistency of assessment generation. Trigger automated code generation in case of corrupted code.
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. .
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.
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.
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.
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
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.
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.
- C:\Program Files\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).
The following system requirements must be in place to use MTest:
- Matlab® R2013b to R2021b
- Targetlink® (base suite) v3.X to v5.1
- 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+
- 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:
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).
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.6 (September 2021)
Handling of MARS/MTCD Interface-Files
- The *.io files are now being updated together with the interface analysis without needing to open the Editor. This ensures the correct interface information in particular during the batch runs.
Manual Enumeration Definitions
- Now enumerations are not deleted from the *.io files if they were not found during interface analysis. This allows the manual definition of enumerations next to the automatically inserted definitions. Note: Outdated enumeration definitions should be deleted manually when necessary.
TargetLink Bus Vector Handling
- The interface analysis is now able to handle TargetLink bus vectors. (#9167)
Coverage Filter Information in Reports
- The test report now shows if a coverage filter is configured. (#7767)
Protected Referenced Models
- During testbed generation, protected referenced models are now included correctly into the testbed. (#9229)
Logged Signals in Referenced Models
- This fix resolves a problem regarding referenced models, when signal data is logged in state machines.
Further Bug Fixes
- #7361: In case the user aborts the batch execution manually they will now be informed that the aggregated model coverage data is not available.
- #7356: The execution date in the main GUI now corresponds to the timestamp of the output data for the currently selected execution mode. It is marked as outdated if the input data is newer than the simulation date.