Difference between revisions of "Extensions.StateVariable"
Jump to navigation
Jump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:OTX '''StateVariable''' Extension}}[[Category:OTX-Extension]][[Category:StateVariable]] | {{DISPLAYTITLE:OTX '''StateVariable''' Extension}}[[Category:OTX-Extension]][[Category:StateVariable]] | ||
== Classification == | == Classification == | ||
| − | {{ClassificationExtension | StateVariable | | + | {{ClassificationExtension | StateVariable | Provides different status information to the environment | [[OtxReference#Extensions|OTX Extension]] | - | - }} |
== Introduction == | == Introduction == | ||
| − | + | 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 intension of '''state variables'''. '''State variables''' are the counter part of context variables. It's the mechanism to transport status information from inside a sequence to the environment, while context variables are the mechanism to transport environment information to the sequence. | |
| + | |||
| + | {{Important|'''State variables''' can only be set and cannot read inside OTX. In other words: The test logic shall not be based on the value of a '''State variable'''.}} | ||
| + | |||
| + | {{Important|OTX documents declaring '''state variables''' should be connected to corresponding setting routines which can set the current value of the status in scope.}} | ||
| + | |||
| + | {{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'''.}} | ||
| + | |||
| + | {{Note|Changes of a '''state variable''' shall be immediately reported to the runtime environment.}} | ||
== Checker Rules == | == Checker Rules == | ||
{| {{TableHeader}} | {| {{TableHeader}} | ||
| − | {{TableRowKeyValueList|[[Extensions.StateVariable.StatVarChk001|StatVar_Chk001]]| | + | {{TableRowKeyValueList|[[Extensions.StateVariable.StatVarChk001|StatVar_Chk001]]|State variables shall not read}} |
|} | |} | ||
Latest revision as of 11:01, 7 November 2018
Classification
| Name | StateVariable |
| Short Description | Provides different status information to the environment |
| Class | OTX Extension |
| Base Extension | - |
| Pre-Conditions | - |
| Specified by | ISO 13209-3 |
Introduction
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 intension of state variables. State variables are the counter part of context variables. It's the mechanism to transport status information from inside a sequence to the environment, while context variables are the mechanism to transport environment information to the sequence.
|
Important: State variables can only be set and cannot read inside OTX. In other words: The test logic shall not be based on the value of a State variable. |
|
|
Important: OTX documents declaring state variables should be connected to corresponding setting routines which can set the current value of the status in scope. |
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.
Checker Rules
| StatVar_Chk001 | State variables shall not read |
