MTest - Tool Release Highlights
Highlights in latest versions of MES Test Manager® (MTest) v.7.8
Better Support for AUTOSAR Models
If an embedded coder model is identified as an AUTOSAR model, its model settings are transferred directly to the testbed.
Test Case Generation for Complex Requirements
Test case generation (TCG) from requirements, where the condition combines multiple AND and OR conditions in parentheses, is now supported. This improves the robustness of the TCG especially for extensive and complex requirements.
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?
Release Notes - MTest v.7.8 (April 2022)
Improved Support for AUTOSAR Models
- The use of Embedded Coder AUTOSAR models is better supported now. If the model is recognized as an AUTOSAR model, now the model settings are also transferred to the test bed. This feature is only available for MATLAB 2018b and newer and not in combination with CTC Coverage. (#9785)
Test Case Generation for More Complex Requirements
- We fixed an issue resulting in test case generation sometimes failing to generate test sequences when the condition of the requirement consisted of multiple AND and OR conditions linked together by parentheses. Test sequences are now generated for this type of requirement. (#9488)
TargetLink Models with Simulink Test Objects
- The test bed generation of test objects that are in a TargetLink model but consist exclusively of Simulink elements with virtual buses is fully supported now. (#9787)
Bug Fixes and Stability Optimization
- This release also focused on fixing bugs, optimizing stability, and improving user experience. These affect a wide range of functionalities in MTest, from generating test cases and the test bed to simulation and result evaluation.
- #9857: Very long signals are no longer an issue for the assessment analyzer. Previously, sequences with very long signals could cause MTest and MATLAB to freeze when plotting graphs of passed and failed regions in the sequence-assessment view. This has been fixed now.
- #9854: We fixed a runtime error that could occur when generating the interfaces file of MARS and MTCD and was caused by signals having the same name as protected variables, for example PI. Please note: Some names of MATLAB function, MTCD functions, or special value names in MATLAB are still not valid for use as signal names, for example PI, nan, inf.
- #9853: We fixed a runtime error that occurred when the model's path changed or was temporarily unavailable. This prevented further processing of MTest, even if the model was not needed for this. The adaptation was made for Windows and Linux systems.
- #9852: We fixed an issue where an empty logged signal resulted in signal logging not working at all. This can happen when signals are logged in a subsystem that is not triggered in the test sequence.
- #9851: We fixed an issue with the CTC configuration where an additional TargetLink default configuration file caused the coverage not to be performed correctly.
- #9809: We fixed a runtime error that could occur when the Lismo settings file could not be read. A useful error message has now been added to the reported error, which helps users to find the cause of the problem more quickly.
- #9796: We fixed a bug for simulations with variable step size where the simulation and the result data output was configured by the user for different workspaces. This is particularly interesting for TargetLink models on newer MATLAB versions in which the simulation workspace is always forced to the base workspace.
- #9777: We fixed an error that prevented the automated import of the MTCD test sequences within the batch run. This error occurred in particular for TargetLink projects and when using MTCD in Excel.
- #9740: We fixed a bug where input signals might be assigned the wrong data type if a signal name appears twice in the inports. Please note: If several inputs of a test object have the same name, this is only permissible if they are exactly the same signal! This problem usually only occurs with bus signals.
- We fixed an issue resulting in unnecessary warnings when importing MTCD test sequences from an Excel file.
- We removed unnecessary warnings related to ignoring subsystems in coverage. These warnings are only of interest when running the simulation, but do not provide any useful information when collecting the result data or generating the reports.