What is MTest?

What's new?

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

• Enhanced handling of data logging configuration
  The current data logging configuration of a test bed can now be saved and reapplied. This allows the custom signal logging setups employed for testing purposes to be reused (independent of the original model). In addition, the test bed's data logging configuration can be disabled/enabled without losing its current logging configuration.
• Quick and direct insight into applied tolerances
  MTest now reports the applied tolerances of signal comparisons (e.g. back-to-back tests) in both the test sequence reports and the signal comparison catalog. MTest displays the maximum value maximum value differences (i.e. positive and negative) from the defined tolerances.
• Documentation support for equivalence class definitions of signals in the MTCD test description

► 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
• 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.1 (January 2019)

• Enhanced logging of internal signals (local signals)
• Multiple enhancements for local/logged signals have been added to improve the workflow, especially for test models where not all necessary local signals are already switched on for logging. The current configuration of signals to be logged can be saved by choosing "Save from Test Bed" in the "Execution > Data Logging Configuration" menu.
  Using "Apply to Test Bed", the saved configuration can be re-applied to the current test bed.
  When a new test bed is created, the current configuration is automatically applied to the new test bed. This allows the test bed's logged signal configuration to be different from the test model (and full batch mode application for the configuration).
  Logging of internal signals can be switched off by using "Disable Data Logging". This switched off/on logging state is also applied when creating a new test bed.

• Calculating and reporting consumed tolerances in report and catalog
• MTest now reports information about the consumed tolerances for each signal comparison, in addition to defined tolerances in the respective test sequence reports, as well as the signal comparison catalog.
  Now, you can see if tolerances were used for a Passed result and what the maximal value deviation was during signal comparison. Therefore, for a Failed result, the "necessary" value tolerance for tolerated deviation can be seen directly.
  This allows for a much quicker evaluation and review of signals with used tolerances.

• Defining equivalence classes for signals in MTCD
• MTCD supports the definition of equivalence classes of signals to enable convenient documentation of this information.
  The parser and the validator support the new syntax. Templates are available in the content assist. See the MTest User Guide for examples. (In later versions, the documented equivalence classes will be used for extended features.)

• Enhanced export of xml and new junit (xml) format
• The xml export is now available. The xml file contains test sequence information and test results.
  The junit xml (separate format) contains information on test sequences. It is used in the MTest step of the MES Jenkins Plugin and can be used (only) with the MTest CI license.

• Deleting project elements
• Via a menu option, single or multiple test sequences, test groups, test objects, or test models can be selectively deleted from an MTest test project.

• Enhancements of MTest Specification Editor
• The work status of test cases and groups in MTCD is now supported by an enumeration of valid entries. By entering the appropriate work status you are able to trace your test case definition progress.
  Previous work status entries in existing test specifications - defined as strings - can simply be transformed by using the quick fix in the error message.
  The workspace folder was renamed from "marsWorkspace" to "editorWorkspace". Existing test projects are adapted automatically.
  Signatures for MTCD functions are now provided in content assist. Negative exponents are supported.

• Added new checks for Test Project Protocol (TPP)
• Test sequences with evaluated assessments: Finds assessments that are active but have no evaluation data.
  Requirements are imported to test object: Finds test objects with no requirement document imported.

• Setting testability review status during requirements import
• When the testability property can be automatically calculated during the requirements import (by setting the right options and availability of data), the testability review status is set to 'reviewed (derived)'. This 'reviewed (derived)' value is interpreted as reviewed in the requirements metrics (in requirements catalog and data export). In this way, the manual review of an automatically calculated testability status is no longer necessary.

• Simulation execution in base workspace supported
• MTest normally performs simulation in a secure function workspace, preventing interference with values existing in the base workspace by chance.
  Now, you can select the option simworkspace = 0 in MTest_UserPrefGUI to perform test sequence simulation in the base workspace.

• Test objects with function call outputs directly supported
• Subsystems with function call outputs can now be used directly as test objects. During test bed creation, additional blocks are included around the test object to convert the function calls to scalar signals.

• (Alpha) MTCD test data viewer with quick refresh of inputs and expected outputs
• When defining signals in MTCD, you can view your input and expected output signals quickly by Sequences/Test Data Viewer. After changes have been made in MTCD (and saved), the signal figure can be quickly refreshed by figure menu MTest/Re-Import Test Data and Refresh Plots. The same signals are shown in the figure (using the newly imported data from MTCD). The list of signals to view will be remembered for the test object and can be re-used for viewing signals of other sequences (of the same test object).

• MARS value tolerance for comparisons
• Value tolerances can be applied for comparisons in formal requirements written in MARS. The generated assessment then tolerates the desired deviation for this comparison. Value tolerances can be defined as absolute values using "[+- ]" or relative values in in percent using "[+- %]" after the right-hand side expression in a comparison and for the expected system response. For , all arithmetic expressions known to MARS are allowed, including signals changing over time.

• MARS vector parameter access
• For parameters that are vectors, it is now possible to access the indices using parentheses. E.g.: "parameter PARAM(1)" to access the value at the first index of the parameter PARAM

• MARS enhancement for combined state and event Trigger
• In some cases where "or" was used in the state trigger, the combined trigger was incorrectly calculated, which led to an unexpected behavior.

• Parser enhancements for broader use of expressions
• In earlier versions, it was, at multiple locations in MARS, only possible to define single values and not to use signals or parameters or arithmetic operations. With multiple parser enhancements, it is now possible to use all arithmetic MARS expressions in most contexts, such as timing definitions.
  (E.g.: "... for 3 + parameter delay seconds" or "...SHALL be true within 1 / parameter controlFreqInHertz seconds")

• Workflow enhancements
• Better recognition of local Excel versions for used separator and language, preventing some "unusable" cell selection in Excel files (especially the work status column in MTCD).
• In MATLAB R2015B, there is a bug preventing the full use of the model coverage functionality. MTest applies the necessary work-around (thanks to TMW) for the appropriate MATLAB versions, enabling model coverage and repeated access to the model coverage options dialog.
• When adding a new test evaluation configuration, the example configuration in MTest_SystemOption in the demo directory is used again (and not an empty configuration). In this way, the default test evaluation configuration can be pre-configured by adapting MTest_SystemOptions in the demo directory of your MTest installation.
• The documentation of varied parameters per test sequence in the test report now works again (it was "refactored" in 5.2/6.0).
• Analysis of logged/local signals in 6.0 could lead to a loop when multiple referenced models were used in the test object and one of the referenced models was referenced more than once.
• In Batch mode deleted test sequences no longer stop the execution of batch actions of subsequent test sequences.