Difference between revisions of "Simulink Tester for T-VEC"

From T-VEC Wiki
Jump to: navigation, search
Line 49: Line 49:
  
 
==Assertions==
 
==Assertions==
 +
 +
==Test Driver Generation==
 +
 +
The Simulink Tester provide test driver schemas for the ERT and GRT code generators supported by the Mathworks RTW, as well as the Matlab Simulator. Howevever, target execution environment have differences, and the tools provide a general purpose test driver template/schema language for describing a generic test driver that can then be instantiated with test vector information by running the test driver generator. An organization can create any number of test driver scripts/programs that are targeted to specific target environments. Schemas can be created from scratch or tailored from schemas provided with the tool installation.
 +
 +
In the case of LDRA's TBRun environment, the installation provides a few default test driver schemas that are designed to produce .tcf  files. These are located in the install area, normally in the directory
 +
 +
  C:\t-vec\translators\sl2tvec\test_drivers
 +
 +
Schemas are provided also with the TTM training examples that are normally located in the directory
 +
 +
  C:\t-vec\examples\ttm\course\exercise_answers
 +
 +
Specific differences in build environments require customization of one of these general purpose schema. To illustrate, one of these example schemas (testbed_tcf_ghs.sch) was created specifically for a Greenhills Compiler environment. The only other task is configuring the object mapping files that are descriptions of how to relate model names with target code names. Some of the object mapping information is automatically set up by the translator, but some of it needs to be identified and added to the mapping information. In a Simulink environment, only some of the necessary information is available to the translator to help in automatically creating the necessary object mappings for the ERT or GRT code generators. Simulink/Stateflow does not provide any form of API for querying this kind of information, but some of it is extracted by executing functions against the RTW. If a different coder is used, or a customization of the default GRT or ERT coder is used, this mapping information needs to be completed by the user.
 +
 +
There is information in the manuals and user's guide about the test driver generator mechanism, but it is also covered in training classes or workshops.

Revision as of 14:27, 19 May 2007