MTest: Frequently Asked Questions
Some of the most frequently asked questions are listed below:
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?
You can access the MTest support website at https://model-engineers.com/support/mtest-support where you can submit a support request. Alternatively, you can contact the MTest support team directly via email firstname.lastname@example.org or telephone at +49 30 2091 6463 40.
The following system requirements must be in place in order to use MTest with MATLAB®, Simulink®, Stateflow®, Embedded Coder®, and TargetLink®:
- Microsoft Windows® operating system
- MATLAB® R2011b to R2020b
- Simulink® and Stateflow® (according to the corresponding MATLAB® version), depending on the models you wish to test
- (Optional) TargetLink® v 3.x to 5.0 (base suite)
- (Optional) Embedded Coder® inside R2011a, R2011b, R2012a, R2012b, R2013a, R2014a, R2014b, R2015a, R2015b, R2016b, R2017b, R2018b
- (Optional) Oracle Java SE Runtime Environment 8, 64 bit, or newer (for use with the MTest Specification Editor)
MTest is compatible with MATLAB® R2011b to R2020b.
MTest is compatible with dSPACE TargetLink® v3.x - v5.0 (base suite).
You can download the latest version of MTest at https://model-engineers.com/support/download/.
MTest ships as a zip file. Unzip the file into a folder. Include the ...\MTest\bin directory in your MATLAB® path (only the \bin directory). Please note: You need write access to these directories (some files are rewritten during MTest execution).
MTest ships with three license options available. Information on the steps necessary to set up an installation for each license model is available at:
For all license types, you can retrieve info on the license currently used directly from the GUI (Help ▷ View License Info), or via the command line (after you have opened MTest):
>> MTest_getLicenseInfo<br< When using MTest within a CI environment license injection is performed by the MES Jenkins Plugin, provided it has been configured properly. For more information about the MES Jenkins Plugin please contact email@example.com.
There is an ISO 26262 Qualification Kit available. It provides a framework
- to determine the required level of confidence in a software tool, and
- to qualify a software tool to create evidence that the tool is suitable to be used to tailor the activities or tasks required by ISO 26262,
so that the tool user can rely on the correct functioning of the software tool for those activities or tasks required by ISO 26262. The ISO 26262 Qualification Kit includes a wide set of document templates (e.g. tool application guide, tool criteria evaluation report, tool qualification report) as well as a user guide. The official certification is in progress.
Yes. MTest supports testing units and integration testing of models with regard to ISO 26262. Moreover, the verification of software requirements is supported by
- a requirement-based method for specifying tests (including functional test case generation),
- requirements traceability,
- the measurement of requirements coverage and structural coverage,
- back-to-back testing of MiL/SiL/PiL, and
- regression testing.
In general, all Simulink®- and Stateflow®-based models can be tested, which includes TargetLink® models.
In principle, all subsystems and Stateflow® charts can be handled as test objects.
MTest provides several approaches for coming up with a requirements-based test case specification:
- Manual test case specification: Using MTest’s own test specification syntax (MTCD), that allows you to define test specifications
- Test case variation: Allows for specification of logical test cases (using MTCD syntax) from which actual test cases are derived automatically
- Functional test case generation: Based on formalized requirements (using MARS) test specifications are automatically generated based on the requirements’ trigger conditions
Regardless of which approach you use, MTest is capable of generating the actual test cases automatically (including the provision of test data).
After selecting a subsystem, the test environment is generated separately from the source model. During automatic creation the source model’s configuration, the signal specifications and parameters are detected automatically and carried over to the test environment.
MTCD is short for Model Test Case Design. This is a method to structure, implement, and document requirements-based tests. It increases efficiency while securing requirements traceability in comprehensive test projects.
The MTest Assessable Requirements Syntax (MARS) is a natural language pattern, based approach to formal requirements. MARS was developed by MES in order to increase the quality of software requirements. It enables the specification of concise, unambiguous, and verifiable requirements that are easy to read and formulate. A MARS requirement is transferred automatically into an MTest assessment function that will act as a requirement observer while evaluating test data in MTest.
MTest is able to automatically create functional test cases that aim to stimulate the requirements’ trigger condition for certain types of MARS requirements. This reduces the effort and time required for manual test case development.
MTest provides several approaches for coming up with a requirements-based test case specification:
- Functional test case generation: Based on formalized requirements (using MARS) test specifications are automatically generated based on the requirements’ trigger conditions and the model’s signal specification (e.g. data type, signal range, and resolution).
- Test case variation: Allows for specification of logical test cases (using MTCD syntax) from which actual test cases are derived automatically.
MTest manages test projects hierarchically. Test projects can include multiple models that may contain multiple test objects (i.e. test items). Your test cases can be bundled by means of test groups (i.e. test suites).
MTest supports the import of requirements via Microsoft Excel® or ReqIF format. MTest enables you to export your test results via HTML and XML format. Formalized requirements can be exported via Microsoft Excel® and ReqIF.
MTest supports the import of requirements via Microsoft Excel® or ReqIF format.
You can formalize your requirements using the MTest Specification Editor. Formalized requirements can be created easily and used for automatic generation of test cases and test assessments by means of templates, content assist, and syntax highlighting.
When specifying test descriptions with MTCD each test case has an attribute containing the requirement ID. This is the only information MTest needs to create the trace between requirements, test cases, and your test evaluation results. Moreover, test cases can refer to multiple requirement IDs.
Using MTest’s own test specification method (MTCD) it is easy to load measurement data from different file formats such as ASCII, MAT, and Microsoft Excel®.
MTest supports the data logging of internal signals for Simulink®, Stateflow®, and TargetLink® models.
MTest handles code generation for you. It supports the code generators TargetLink® and Embedded Coder. Once code generation is invoked MTest automatically incorporates the code into the test environment.
The easiest method for checking your model’s requirements compliance is to use test assessments. Assessments are requirement observers that functionally evaluate your test data. Based on formalized requirements (MARS) assessments are created automatically. However, you can also create them manually.
The MTest test documentation reports a metric measuring the linkage of at least one test case to a respective requirement. Moreover, in-depth tracing information is provided as well.
MTest provides comprehensive batch test capabilities including a large list of possible batch actions such as test data import, test harness creation, code generation, MiL/SiL simulation, test evaluation, test documentation, and so on. Furthermore, MTest can be used within a Jenkins automation server by means of the MES Jenkins Plugin. For more information on MES Jenkins Plugin please contact firstname.lastname@example.org.
MTest supports the export of test results via XML and HTML format. Formalized requirements can be exported via Microsoft Excel® and ReqIF files.
MTest and MXAM both require Java libraries. MTest and MXAM must initialize their paths in a separate step, before executing either tool. MTest ships with a demo initialization script that helps you with setting up your environment.
In MTest, important test artifacts (e.g. test cases and assessment) possess status attributes mapping onto their respective work progress. This data is taken into consideration for computing a quality/progress metric for your test project. Moreover, MTest can check its test projects with regard to their levels of completeness, correctness, and consistency.