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.

What's new?

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

► 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 R2018b
  • 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

User Guide

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

Release Notes

MTest v 6.3 (July 2019)

  • (Beta) Test case generation by variation in MTCD
      Test sequences can be generated using logical test cases in MTCD in the MTest specification editor. The logical test cases can contain any number of variation points. Each variation point is defined by a variation list. During test sequence import concrete test sequences using the defined variations are derived from the logical test cases. The number of generated test sequences depends on the defined variation points and the number of elements in each variation list used. Currently a full variation algorithm is used to generate test sequences.
  • (Beta) Logged signals utilization in signal comparisons
      Signal comparisons were extended to logged/local signals (in addition to output signals). Logged signals can be used in regression, back-to-back and expected output comparisons. To activate logged signal comparisons for respective evaluations, please enable this feature in MTest_UserPrefGUI by the options:
      • PropGUIDefault.evaluation.comparelocalsignals.Regression = 1;
      • (respective BackToBack = 1; and ExpectedOutput = 1;)
      Definition of tolerances is supported for logged signals as well. You find the logged signal names in the tolerance option file. These logged signal can be recognized by the extension "(logged)". The results of the comparisons are reported in the evaluation section of the test sequence report, in test sequence catalog, and in signal comparison catalog.
  • Ignore specific signals in signal comparisons by INF tolerance
      To exclude/ignore some signals from signal comparisons, just define a tolerance of Inf for these signals. If any of the value tolerances or the time tolerance is Inf, this signal is evaluated to NOT ACTIVE. This result is reported in the respective reports and catalogs. It is visible by design, but will vanish during result aggregation.
      This excluding configuration applies to all test sequences of a test object for the respective signals.
  • Improvements in Interface Analysis
      When a BusCreator is found the Interface Analysis takes all the information from the BusCreator-Struct on output and input side. On input side there was an additional effective interface analysis, which could produce incorrect interface structures. (#6888)
  • Support for configuration references in SLDD
      Configuration references in SLDD are handled by MTest now. It is ensured, that SLDD of testbed and model are not open at the same time, when a model update/compile is performed by MTest. (#6906)
  • MARS: 'inbetween' with open and half-open intervals (include, exclude)
      For the inbetween definition it is now possible to define the exclusion of the boundaries by using the keyword exclude. The keyword include was also added but it defines the default behavior. (#6857)
  • Measurement data initialization in MTCD in expected order
      For the import of measurement data using MTCD, the order of initialization of signals was improved. Definitions in the test sequence have precedence compared to definitions in the test group.
      It is still possible to "overwrite" signals of the measurement data (or add missing ones) by defining them in the initialization or action field of the respective test sequence.
  • Master-slave support for MTest step in MES Jenkins PlugIn
      The MTest step of the MES Jenkins PlugIn supports Master-slave now. An MTest-CI-License is necessary to use this feature.