Difference between revisions of "Simulink Tester Issues"

From T-VEC Wiki
Jump to: navigation, search
(Test Sequence Vectors)
Line 66: Line 66:
  
 
The default is to generate vectors for both cases, 2 vectors per DCP when no state variables are available, but T-VEC produces 4 vectors when state variables are available.
 
The default is to generate vectors for both cases, 2 vectors per DCP when no state variables are available, but T-VEC produces 4 vectors when state variables are available.
 +
 +
===Test Driver Generation===
 +
There are some situation where manual support is needed for test driver generation in both Simulink and Stateflow models where some inputs not available from RTW. There are cases where it is simply not possible to predict variable names, function parameter orders, etc. There is no API for determining the choices made by the RTW to fully automate all aspects of test driver map file creation.
 +
 +
There is a work around with the current schemas - all mapping descriptors are passed through a Perl function before going into the target file. The perl script parses in an external file that contains new replacement mapping information. The mapping can be either by the descriptor itself or the mapping key. If the perl script finds a match then it uses the replacement from the file.  This function can be extended directly through the Perl script.

Revision as of 15:20, 25 February 2007