… for use with Simulink®, Stateflow®, and code generation tools
IntroductionMonkeyProof Unit Test Manager provides a centralized, single-environment, automated and traceable environment for verification of Simulink designs. Costs are cut by automating repeat testing and reporting necessary whenever a model changes, different parameters and/or different test scenarios apply, and when the hand written or automatically generated code for HIL or SIL testing is available. Quality is impacted by making tests reproducible and by providing centralized traceability of test results to the requirement under test, to the applied parameter settings and test vectors under test, and to the model and model version under test.It is tightly integrated with MonkeyProof Requirements Manager and MonkeyProof Data Dictionary manager to provide full traceability and role and user based permissions when used in a hierarchical collaborative design environment. |  | |
Key features
| ||
Reuse, repeatability, traceabilityThe Unit Test Manager is designed to manage and provide control over a structured test process as an integral part of a model based design approach. At any level and stage in the design process input-output behavior can be tested and reported upon in a repeatable manner. Tests can be hyperlinked to requirements in the MonkeyProof Requirements Manager to provide traceability that facilitates verification.All test case components are cleanly separated and centrally administered allowing efficient reuse when testing variants to model, parameter, or scenario. |  | |
Test caseEach individual test case under MonkeyProof Unit Test manager consists of the following versioned components: model under test, test harness model, input vectors, and parameter settings (calibration values). Meta data such as summary, description, rationale, link with requirement, etc is also part of the test case. Test results, both numeric and automatically generated test report are part of the test case.Meta data is stored in database for searching and unique reference and relation definition. All other data is stored in a central (versioned) repository. Test vectors and parameter settings can be shared between test cases. |  | |
Test harnessSimulink test harness models are automatically generated based on the I/O definition of the model-under-test and the selected test type or template. All Simulink data types and busses are supported. Test types are user customizable through Simulink model test harness templates. | ||
Input vectors and parametersInput vectors and parameter values can be reused between test cases. Parameter values are set from user selectable M-scripts. Multiple parameter scripts can be combined for one test case.Test vectors are modified using the Simulink Signal Builder Block interface. Test vectors are stored separate from model allowing reuse by other tests. | ||
Test resultsThe results of a Unit Test Manager test run consist of model-under-test inputs, outputs, intermediate signals set to be logged (model setting), and a coverage report. Results can be stored for reference, compared with earlier results (regression testing) and signals can be visualized and analyzed using MathWorks Time Series Tool. |  | |
Usability – one design environmentMonkeyProof Unit Test Manager is built to operate seamlessly with and within the familiar MATLAB/ Simulink model based design environment of the engineer. No switching between different environments is required. It is integrated with MonkeyProof Requirements Manager to facilitate requirements based testing and easy verification. | ||
System & platform requirementsMonkeyProof Unit Test Manager is supported on MathWorks’ release 2007b and up. MATLAB, Simulink, and Simulink Verification and Validation are required. | ||
| * Out of the box the central database backend is implemented in Microsoft SQL (Express) 2005. ** MATLAB Report Generator is required for reporting | ||