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.

Highlights in latest versions of 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.

 

MTest v.7.4

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

MTest v.7.3

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.

MTest v.7.2

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.

MTest v.7.1

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.

MTest v.7.0

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

MTest v.6.4

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.

MTest v.6.3

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

 

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.

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

System Requirements

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+

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

MTest User Guide

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.5 (June 2021)

Provision of Enumerations for Use in the MTest Specification Editor

  • With this version, MTest is able to automatically provide the test object's interface signals and workspace parameters of type enumeration (including their members) for use in the MTest Specification Editor. Both signals and parameters are now automatically written to the *_interface.io file. Note: Test sequences cannot be generated from MARS requirements that contain enumeration expressions in their trigger formulation.

Possibility to Provide a Default Configuration

  • There is now a way to provide a standard configuration for the MTest projects that need to rely on one. For this purpose, the function <MTESTROOT\bin\AddOn\ConfigMan\MTest_getConfigData.m> is delivered as source code with this release. The values of the variable "DefaultValue" can be adapted individually for each configuration parameter in the source code. Please note: Changes are only allowed to the variable "DefaultValue". Any changes to other variables (e.g. Section, Name, Levels) may cause MTest to malfunction.

New Option for Signal Data Type Analysis of TargetLink Subsystems

  • In this version of MTest a new configuration option has been added to specify at which interface level the signal data types of TargetLink subsystems are to be analyzed: either at the outer boundaries of the TargetLink intermediate layers or directly at the TargetLink ports of the actual TargetLink subsystem. For this purpose we introduced the parameter TargetLinkPortAnalysisSource. It can have the following values:
    • 0: The interface data is analyzed at the Simulink ports of the TargetLink subsystem, i.e. at the ports located within the Simulink subsystem which is two levels above the actual TargetLink subsystem.
    • 1: The interface data is analyzed directly at the TargetLink ports of the TargetLink subsystem.
    • The default value is 1.

Support for Displaying Complex Signals in the Assessment Analyzer

  • In order to display complex (mathematical) signals (e.g. a = sqrt(-1)) in the Assessment Analyzer, they are now split into their real and imaginary parts and displayed separately.

Further Bug Fixes

  • #7929: This fix corrects a misbehavior where after deleting a MARS requirement, the associated generated assessment persisted. Now it is ensured that only generated assessments based on valid MARS requirements exist.
  • #8557: This fix ensures that the port names are used for output buses if the setting of the configuration parameter is "SourceForSignalNaming = 1". In the past it happened that despite this setting the signal names were applied for use in MTest.
  • #8671: This fix ensures that generated code is properly simulated during Embedded Coder SiL. Previously, it could happen that in SiL mode the MiL test bed was mistakenly used for simulation. Now, the batch test ensures that, if no code is currently available, it is also generated before a SiL simulation, even if the "Code Generation" batch action is not active.
  • #8992: This change fixes the bug where the batch test crashes if there is no interface file and the batch action "Regenerate Testbed" is selected.
  • #9014: This fix suppresses the output of a specific warning message when applying model coverage filtering to items inside linked libraries. In addition, improved error handling has been introduced in case the above filtering is applied in conjunction with activated TargetLink code coverage filtering.
  • #9063: This change ensures that the user gets an explicit feedback in case the conversion of the system under test to a referenced model fails (e.g. a masked test object that defines initialization code in the mask). Previously, this could lead to an easy-to-overlook failure when trying to set up the coverage.
  • #9076: This fix eliminates the Test Data Viewer crashing when trying to display expected output signals in case the corresponding data file is empty.
  • #9088: This fix resolves a testbed simulation failure due to a version mismatch of referenced models within the testbed. Now the model reference block within the testbed is automatically refreshed during testbed generation.