 |
OTX Reference
|
|
|
OTX Reference
|
|
DEPRECATED - Use otx:StateVariableDeclaration instead. More...
Namespaces | |
| namespace | Declarations |
| Extension specific declarations | |
Classes | |
| class | CheckerRule |
| Comprehensive checker rule listing, see also Core checker rules. More... | |
DEPRECATED - Use otx:StateVariableDeclaration instead.
Test sequences require a technique to provide different status information to the environment, e.g. progress of execution or currently selected ECU, etc. This is the intention of state variables. State variables are the counter part of context variables. They provide the mechanism to transport status information from inside a sequence to the environment, whilst context variables are the mechanism to transport environment information to the sequence.
IMPORTANT - Procedures can write to any visible state variable. Every time this happens, the new value of the state variable becomes available to the environment. As a convenience to the OTX author, it is also possible to read the current value of a state variable; however, this functionality is limited to state variables with PRIVATE visibility.
IMPORTANT - OTX documents declaring state variables should be connected to corresponding setting routines which can set the current value of the status in scope. Therefore, test applications require a mapping between state variables and according setting routines. The mapping may be kept in application specific places, but it may also be contained in meta-data compartments of an OTX document (cf. 7.16.5). The recommendations for meta-data compartments described in ISO 13209-2, 7.5.3 shall be applied also for state variables.
Note: For technical reasons, state:StateVariableDeclaration is defined as a sub type of otx:ContextVariableDeclaration.Regardless, state variables are not context variables. Statements about context variables do not automatically apply to state variables.
Changes of a state variable shall be immediately reported to the runtime environment.