What is MTest?

What's new?

Highlights in MES Test Manager^® (MTest) v.6.2

Significant performance improvements for Simulink/Embedded Coder users:
Speed-up of batch MiL simulation by using Simulink Fast Restart option.
Speed-up of batch SiL simulations when using tunable parameters in the generated code of Embedded Coder models.

Exclusion of subsystems from model/code coverage:
Already tested submodules can be excluded from model/code coverage measurement during integration testing.

Improved support of Simulink Data Dictionary (SLDD):
Parameters defined in the SLDD can be used and varied in MTCD. The SLDD values are available in MTCD templates, MARS, and manual assessments.

► Read about all new features in the Release Notes

System requirements

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

• Matlab^® R2009b to R2018a
• Targetlink^® (base suite) V3.X to V4.3
• 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).

Installation

• 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

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

Release Notes

MTest v 6.2 (March 2019)

• Speed-up of batch MiL simulation by making use of Simulink

Fast Restart The batch test now allows the use of Simulink's Fast Restart feature for executing of MiL simulations of Simulink and Embedded Coder models. The user can activate this option via a dedicated check box in the Batch Test GUI.
The Fast Restart is only available in the following versions:
• MATLAB R2014b and newer
• TargetLink 4.4

Furthermore, the Fast Restart only allows to simulate test sequences sharing the same step size. In case of varying step sizes the test sequences selected for batch execution will be simulated using the step size of the first test sequence.

• Speed-up of batch SiL simulations by using tunable parameters

User of Embedded Coder models can now significantly reduce the SiL simulation run time during batch test by omitting code generation prior to each SiL simulation. This feature is also applicable to test sequences containing parameter variations.
If MTest detects that the configuration setting 'DefaultParameterBehavior' of the test bed is set to 'Tunable parameters', the batch test will generate the code only once for each test bed.
Hint: You can check this setting via:
• get_param(gcs, 'DefaultParameterBehavior')

Please note:

The feature is only available in MATLAB R2015b and newer and Embedded Coder.

• Exclusion of subsystem(s) from structural coverage computation

For a selected test object the user can now define an ignore-list of subsystems. Those subsystems will then be excluded from the computation of the structural coverage. The ignore-list will affect both model coverage and code coverage.
Regarding code coverage the feature is available for the TargetLink Code Coverage tool (TL only), as well as for Testwell CTC++ (TargetLink and Embedded Coder).
In particular, this feature is beneficial in terms of testing activities on integration level or subsystems utilizing library instances.

• Enhanced interface analysis

The interface analysis now supports two-dimensional array signals.
With this version Nx1 and 1xN arrays are supported.
In addition, MTest is now able to analyze array signals whose data types are defined via custom data types defined in the Simulink Data Dictionary.
Furthermore, the interface analysis is now also capable of handling signals that are defined as bus elements within a Simulink bus object that in turn is defined in a Simulink Data Dictionary as well.

• Support of parameters defined in the Simulink Data Dictionary

Parameters defined in a Simulink Data Dictionary are now available for use with MARS and MTCD. The parameters are read from the Simulink Data Dictionary and their actual values are used for the general test group initialization. Of course, they can be varied like any other parameter from workspace.

• New MTCD signal function 'gradientsteps'

With the help of the signal function 'gradientsteps' the user can now gradually increase/decrease the signal's value similar to the existing function 'gradient'. Now it is possible to define for how long the intermediate signal values shall be held constant, resulting in a step-like signal shape.

• General update of MTest Specification Editor

When the MTest Specification Editor is opened the entire Eclipse project will be refreshed, resulting in an update of the project structure and the automatic detection of newly created files.

• MTCD supports import of measurement data from ASCII and Excel files

In reference to the import of *.mat files, MTCD can now handle the import of test data from ASCII files, as well as Microsoft Excel files.

• New check for Test Project Protocol available

The introduced check compiles a list of test sequences that have been evaluated manually. This helps to detect any differences between automatic and manual evaluation and thus helps tracking manual results (e.g. to avoid unintentionally overwriting test results).

• The MTest Demo Project received an update

The major change is constituted by the addition of MARS and MTCD examples in text format. That way, the user is now enabled to get a first impression of the text-based MTCD editor and to get familiar with MARS already at an early stage.

• Acceptance of MES End-User License Agreement

Upon first start of the current MTest release, the user is asked to accept the MES End-User License Agreement (EULA). At this, the user has the option to view the EULA in English or Chinese language. MTest will not start unless the EULA is accepted.

• Enhanced data logging workflow

While working with logged signals defined in the testbed, the data logging of Simulink and TargetLink signals can now be enabled/disabled separately.
For this purpose, two entries in the MTest main menu are available.
Here, available options do reflect the current state of the configuration.
Most important to note is that the Simulink data logging must be enabled specifically by the user if a TargetLink user wants to log Simulink signals (e.g. elements of Stateflow charts).
In the past, Simulink data logging was always enabled which could have lead to problems in the case of signals being logged by both mechanisms.

• Display of aggregated results in Manual Evaluation dialog

The aggregation of automatic evaluation results now includes the results of the comparison to expected outputs defined in the MTCD test description.

• Selection of reference data

If the user selects any data for use as reference from sources for which no data is available, the user receives more helpful feedback.

• Handling of models with no subsystems

When selecting a model that does not contain any subsystem the user receives feedback via a descriptive dialog box.
In addition the handling of the Data Logging Configuration for testbeds that refer to models that do not contain any subsystems will now be handled correctly.