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.7
Support for Enumeration Definitions in Simulink Data Dictionary
For enumerations that are defined in a SLDD, the symbolic names of their members can also be used in MTCD and MARS now, instead of using the numeric values.
Undefined Areas in Logged Signals
During signal logging there may be time intervals where signals are not defined (e.g. due to logging of states or triggered subsystems). These undefined areas can now be filled in by holding the last valid value in order to improve assessment evaluation and reporting.
Highlights in 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.
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.
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
Installation
- 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.
In order to run MTest and MXAM at the same time, run their path functions in a separate step:
- 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.
License Configuration
Learn more about the MES Quality Tools License Configuration, general license questions and the MES licensing models as well as how to change your MAC-ID.
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® 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+
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
Suggestions
If you have any suggestions to help us improve the MES Test Manager® (MTest), please do not hesitate to contact us:
Email: mtest@model-engineers.com
User Instruction
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.7 (December 2021)
Support for Enumeration Definitions in Simulink Data Dictionary
- Enumeration Definitions with Numerical Values in MTCD & MARS Interface File
In addition to the symbolic name, the numerical values of the enumerations are now also written in the MARS and MTCD interface file with the extension *.io.
Likewise, numerical values can be assigned for manually added enumerations too.
This makes it possible to use the symbolic name of enumerations instead of the numerical value in MTCD and in MARS for signals and parameters, if a model has SLDDs set as workspace. It may be necessary to carry out a new, once-off interface analysis and a re-import of the test sequences. - Proper Closing of Simulink Data Dictionaries
When creating a testbed, MTest also creates a copy of the original SLDD from the model. This ensures that the test does not alter the original model and that a reset of the test data can be done between simulations. If enumerations are used within the SLDD, the alternating access to the SLDD of the model and the test-bed often leads to problems in MATLAB, since enumeration definitions may only exist once.
To minimize these conflicts, a new option has been introduced to close the model and the testbed with their associated SLDDs whenever necessary. This option is available for Embedded Coder models in MATLAB 2018b and newer, as the correct functioning can only be guaranteed here.
The new parameter for this is "SupportEnumDefinitionsInSLDD" and can be found in the menu under "Manage Project Configuration" or in "MTest_Configuration.m".
Undefined Areas in Logged Signals (#9343 & #9389)
- During signal logging there may be time intervals, where signals are not defined e.g. due to logging of states in state machines or triggered subsystems. If no values are available for time steps, these are provided in MTest by default with a NaN value so that all the signals have the same format for further processing. In this way, the results show only the values that the simulation actually determined. However, writing assessments or interpretation of the data can be easier if NaN values are replaced by the omitted numerical values in the signals. Therefore, these undefined areas can now be filled in by holding the last valid value to improve evaluation and reporting.
The new parameter for this is "LoggedSignalsFillNaNs" and can be found in the menu under "Manage Project Configuration" or in "MTest_Configuration.m".
Bug Fixes
- #9532: Improved error message that shows during report generation caused by using project paths that are too long.
- #9517: Support for the TargetLink properties 'Inherit' and 'Uniform Elements' on bus signals when building a test-bed.