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.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® 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+
- 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.3 (December 2020)
- Embedded Coder Code Coverage
- Simulink Coverage is only available for MATLAB R2018b and newer
- Coverage ignore mechanism is not supported
- Users of embedded coder models can now also collect their code coverage using the Simulink Coverage Toolbox. For this purpose, the creation of the testbed has been changed. The selected test object is converted into a referenced model and automatically inserted into the testbed. In order to be able to use the Simulink Coverage Toolbox, the corresponding project configuration must be adapted. The parameter CovEmbeddedCoderCodeCoverage was introduced for this purpose. The parameter can have the following values:
- 0: Testwell CTC++
- 1: Simulink Coverage
- The default value is 0.
- The following limitations remain in effect:
- Batch Creation of Assessments
- In this new version it is possible for the user to generate assessments from MARS requirements within the batch test. For this purpose a new Batch Action (Regenerate Assessments) is available within the Batch Test GUI.
- In this context, the GUI layout of the available batch actions has also been redesigned. In particular, the options for updating (or regenerating) (MARS-based) test elements are now arranged more clearly.
- Please note: Before executing the batch generation of assessments from MARS requirements, the corresponding storage directories of the assessment files are deleted each time.
- Automatic Read Out of Signal Characteristics of Bus Elements (#8535)
- The test case generation has been improved in that the signal characteristics of bus elements are automatically read out from the test object input interface and from signal attribute definitions defined higher in the model hierarchy (if the model is compilable). The user no longer has to enter this information manually in the _interface.io file.
- Further Bug Fixes
- #8472: Previously, function calls were being misinterpreted as data type, resulting in them being used in the data type conversion block. This lead to errors when trying to simulate the testbed. This has been fixed now.
- #8566: This solves the issue of MARS assessments not being counted and displayed in the main GUI and evaluation configuration GUI. However, they have always been evaluated.
- #8591: With this fix we solved the problem of losing the filter configuration when leaving the changed testbed unsaved, and the user (or MATLAB) closes the testbed. Now we save the testbed after changing the coverage filter settings.
- #8652: This fix supports the specification of relative paths within the testbed's TargetLink Data Dictionary using '.\' as well.
- #8658: This fixes an issue of logged signals not being available to the assessments. This could have occurred in the batch mode in case both the MiL and SiL simulation were activated at the same time.