What is MTest?

What's new?

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

• Advanced editor for MTCD test case specification:
  The MTCD (Model Test Case Definition) editor provides comprehensive support for specifying test cases. Convenient templates simplify the tasks, and online syntax validation directly indicates possible issues before importing the test cases.
• Better interface change management: The interface change analysis and management feature directly reports any changes to the test object interface and supports auto-updating of any interface data throughout the test project.
• Batch function delivers status information and fulfillment of success criteria in continuous integration with Jenkins

► 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 R2017b (höhere Versionen wie R2018a funktionieren auch, aber sind noch nicht in unserem Systemtest enthalten. Darum ganz sicher: bis R2017b. Simulink, Stateflow, Embeded Coder sollen hier implizit bedacht sein)
• 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.0 (September 2018)

• MTCD text editor as part of MTest Specification Editor (Eclipse)
• MTCD can be written and edited in a dedicated Eclipse/text editor - the MTest Specification Editor (also used for MARS).
  This MTCD editor has no limits for the length/size of a test sequence or parameter definitions (as Excel has).
  The editor provides templates for test group, test sequence, signal names, parameter names, MTCD functions, and more.
  The written MTCD is validated online and helpful hints are shown. An outline view and navigation and the many other usual editor features are also available.
  The Excel MTCD can be converted to a text MTCD (menu).
  The MTCD specification by Excel is still available.

• Automatic adaptation to changes to the test object interface
• When changes are made to the test object interface, MTest reports these changes (diff analysis: new/renamed/deleted signal).
  These changes can be checked, mapped (i.e. from new to renamed), and confirmed.
  Using this mapping function, the interface changes can then be disseminated to MTCD, MARS, reference data, test setup, tolerance definitions, and further definitions in MTest.
  In addition to storing the current interface definition, MTest also stores the history of the interface (different baselines). This way, interface changes can be mapped on the basis of one of the previous interface baselines.
  A mapping GUI provides an intuitive way of mapping and selecting dissemination actions.

• Batch functions return extended status information
• The MTest batch functions (MTest_BatchProject and MTest_Batch on a lower level) return extended status information. This aggregated value for all performed batch actions provides one result regarding everything OK (1), something not OK (-1), or nothing done (0).
  For CI (Continuous Integration), a success criteria can be used to provide a success value even when the results of a test evaluation were 'failed' (but nothing aborted or errored). This is useful to get a stable result in Jenkins, even when not all evaluations have the result 'passed'.
  A CI license for MTest is necessary to use this feature.

• Batch configurations/selections in MTest_BatchProject
• Batch selections saved in Batch GUI (in a mat file in test project) can be used to configure a batch run in MTest_BatchProject (and in the MES Jenkins Plugin).
  These batch selections must be created/saved in MTest 6 or newer.
  Batch selections should only be used for specific use cases.
  The direct definition of test models/objects and batch actions for
  MTest_BatchProject is much more visible.

• MTest step in MES Jenkins Plugin
• The MES Jenkins Plugin contains an MTest step. Please see the documentation of the MES Jenkins Plugin.
  A CI license for MTest is necessary to use this feature.

• MARS enhancements
• Defines representing a scalar value not dependent on simulation data are now properly set as parameters and are used as such in the generated assessments.
  The number of supported arithmetic functions has greatly improved.
  Additionally, it is now possible to use arbitrary function names for user-defined functions.
  The "^" operator is now available to potentiate in arithmetic expressions.

• Inclusion of test sequence report graphics directly in HTML report
• The graphics of the HTML test sequence report can be included inside the HTML report (as base64 data).
  In this way, the number of files in the test project is now much lower.
  This graphic inclusion can be switched off in MTest_UserPrefGUI by PropGUIDefault.report.embedimagesbase64.

• Option to skip extra interface analysis if model did not change
• Before an interface analysis is performed, MTest can checks if the model to test really changed since the last interface analysis. If no change was detected, the still current interface information is used.
  Multiple conditions are checked (if any changed, interface analysis is performed): modification of model, modification of referenced models, modification of Testsetup files.
  This option must currently be enabled in MTest_UserPrefGUI by execution.forceinterfaceanalysis = 0 (disable force interface analysis)

• User Guide v 6.0
• The MTest User Guide contains descriptions of the interface changes workflow.
  The MTCD text editor in Eclipse is explained as part of the MTCD Chapter.
  Details about the extended batch features are described in the Batch Chapter.

• Workflow enhancements
• A few of the settings in MTest_UserPrefGUI were changed to reflect the settings most customers of MTest use (this is a major release).
  Please check your previous usage of these settings and adapt if necessary.
  A paused batch run can be resumed again (introduced in MTest 5.2).
  The signal catalog shows all test groups (and not just the last one).
  The baseline (version info) of the requirements document (RSD) is shown in the start of the requirements catalog (it was already visible in each requirement).
  During test bed generation and the TL module enhancement, further output parameters are transferred to the test bed: InitialOutput and OutputWhenDisabled (reset method).
  The MQC XML export was extended to support different naming of model coverage methods in different Matlab releases and really exports the structural coverage values of multiple test objects.