Release Notes - MTest v.7.8.1 (July 2022)
Bug Fixes and Robustness Improvements
This release mainly focuses on fixing bugs and improving robustness and user experience. These affect a range of functionalities in MTest, e.g. test bed generation, project configuration and test execution.
- #9683: We added additional modes for the BusElementRenaming option. This option adds the bus structure to bus signal names as a prefix, in case different buses contain signals with identical names.
If the bus structure has too many hierarchies, the two new options prevent the signal names from exceeding the maximum number of 73 characters, by shortening the prefix at the beginning or the end.
A detailed description can be found in the configuration documentation.
- #9804: We fixed an issue related to the InheritInputDataTypes option. If the input interface of a test object contains vector signals in buses, the signals are no longer converted to a specific data type, in case this option is activated.
The "Data Type Override (True Doubles)" option is now reset in the test bed after each batch run. Rebuilding the test bed is no longer necessary, when the option is deactivated again.
- #9911: We have accelerated the textual output of vectorial values, which means that reports and catalogs are now generated faster. This will be particularly noticeable when outputting larger vector parameters.
- #10013: If a test sequence is deleted using the menu, the associated coverage data is now also properly deleted. This affects both the coverage data of the test sequence itself, and the aggregated coverage data for the test object, ensuring that no inconsistent coverage results are shown in the reports.
In order to get the correct aggregated coverage values of the test object, only one test sequence has to be executed again, with coverage enabled.
- #10035: We fixed an issue where the user was not correctly informed if an error occurred during testbed preprocessing. The batch execution now displays a NOT OK as the result.
In addition, there is no longer an attempt to carry out further actions for the test object in batch mode, if the test bed could not be created correctly.
If an error occurs during the execution of a test case when determining the model coverage, the user is now immediately informed of this error. Previously, the test case ran without coverage instead, without reporting that coverage data was missing.
We have updated various chapters of the user guide for better understanding.
- If you receive MTest in one zip file, please extract it into a folder. Please keep all the subdirectories.
- C:\Program Files\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.
In order to run MTest and MXAM at the same time, run their path functions in a separate step:
- 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.
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 Tool FAQ
How do I contact the MTest support team?
What system requirements do I need to run MTest?
Which MATLAB® versions are MTest compatible with?
Which TargetLink® version does MTest support?
Where do I download the latest version of MTest?
How do I install MTest?
How do I configure my license?
Is MTest certified in any form?
Does MTest support test processes with respect to ISO 26262?
Which types of models can be tested with MTest?
Which model parts can be tested with MTest?
How do I specify my test cases?
How does MTest test my model?
What does MTCD mean?
What does MARS mean?
Is it possible to generate test cases with MTest?
How do I generate test cases?
How should I structure my test suites?
How do I connect MTest with my Application Lifecycle Management (ALM) software?
How do I import my requirements into MTest?
How do I formalize requirements?
How do I link test cases to requirements?
How do I include measurement data for use within my test cases?
How do I record signals and states that are neither input nor output signals?
How do I generate and simulate my code?
How do I check if my model meets its requirements?
How do I check my requirements coverage?
How do I run my test projects automatically?
How do I export my test results?
Can I execute MTest and MXAM at the same time?
How do I track my project progress and integrity?