Comprehensive checker rule listing, see also Core checker rules. More...

Public Attributes
Severity.Critical	DiagCom_Chk001
	No Path in ExecuteDiagService response parameter arguments More...

Severity.Critical	DiagCom_Chk002
	Type-safe GetAllResultsAndClear More...

Severity.Critical	DiagCom_Chk003
	Target definition for ResponseParameter More...

Severity.Warning	DiagCom_Chk100
	Access path can not be determined More...

Severity.Critical	DiagCom_Chk101
	Access path can not be resolved More...

Severity.Warning	DiagCom_Chk103
	Incorrect data type in request/response parameter arguments of inline mapping More...

Severity.Warning	DiagCom_Chk200
	The required request parameter in ExecuteDiagService can not be determined More...

Severity.Critical	DiagCom_Chk201
	GetComChannel EcuVariantName must be omitted in case of PVS More...

Severity.Warning	DiagMetaData_Chk100
	Not supported elements More...

Severity.Warning	DiagMetaData_Chk101
	comChannelGroupName or ecuVariantGroupName must exist in DiagValidationGroup More...

Severity.Critical	DiagMetaData_Chk102
	EcuVariantGroup does not match with the ComChannel identifier More...

Detailed Description

Comprehensive checker rule listing, see also Core checker rules.

Member Data Documentation

◆ DiagCom_Chk001

Severity.Critical OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagCom_Chk001

No Path in ExecuteDiagService response parameter arguments

Criterion: The <target> variable in any of an ExecuteDiagService action's response parameter mappings will not be part of a compound data structure like an otx:List or otx:Map.Therefore the <path> member element of <target> will not be used within any ResponseParameter. The same applies to the <textIdTarget> variable.

◆ DiagCom_Chk002

Severity.Critical OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagCom_Chk002

Type-safe GetAllResultsAndClear

Criterion: In a GetAllResultsAndClear action, the list items (given by the <resultList> element) will be of type Result.

◆ DiagCom_Chk003

Severity.Critical OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagCom_Chk003

Target definition for ResponseParameter

Criterion: The XML Schema allows that <target> and <textIdTarget> are optional, but at least one shall be set; it is illegal to omit both <target> and <textIdTarget>.

◆ DiagCom_Chk100

Severity.Warning OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagCom_Chk100

Access path can not be determined

Criterion: The access path can be determined neither implicitly nor explicitly.

Comment: No further validation takes place for the related element.

Attributes: AdvancedCheckerRule

◆ DiagCom_Chk101

Severity.Critical OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagCom_Chk101

Access path can not be resolved

Criterion: Access path can be determined but the target does not exist (wrong path).

Attributes: AdvancedCheckerRule

◆ DiagCom_Chk103

Severity.Warning OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagCom_Chk103

Incorrect data type in request/response parameter arguments of inline mapping

Criterion: In an ExecuteDiagService action, if an invalid OTX data type is mapped to a request parameter or a response parameter is mapped to an invalid OTX data type via inline mapping. For instance if a String variable gets mapped onto a request parameter that is of type Integer.

Attributes: AdvancedCheckerRule

◆ DiagCom_Chk200

Severity.Warning OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagCom_Chk200

The required request parameter in ExecuteDiagService can not be determined

Criterion: In an ExecuteDiagService action, if a request parameter has not been set a value, this checker rule will occur.

Attributes: AdvancedCheckerRule

◆ DiagCom_Chk201

Severity.Critical OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagCom_Chk201

GetComChannel EcuVariantName must be omitted in case of PVS

Criterion: In term GetComChannel if PerfromVariantSelection is TRUE, EcuVariantName must be omitted (NULL). Because it can be result in unexpected behavior at runtime.

Attributes: AdvancedCheckerRule

◆ DiagMetaData_Chk100

Severity.Warning OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagMetaData_Chk100

Not supported elements

Criterion: The DiagMetaData elements used are not supported in this context and are therefore ignored.

Attributes: AdvancedCheckerRule

◆ DiagMetaData_Chk101

Severity.Warning OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagMetaData_Chk101

comChannelGroupName or ecuVariantGroupName must exist in DiagValidationGroup

Criterion: The value from comChannelGroupName or ecuVariantGroupName cannot be found in DVG (wrong path).

Comment: The DiagValidationGroup must be valid against OTX.

Attributes: AdvancedCheckerRule

◆ DiagMetaData_Chk102

Severity.Critical OpenTestSystem.Otx.Extensions.DiagCom.CheckerRule.DiagMetaData_Chk102

EcuVariantGroup does not match with the ComChannel identifier

Criterion: The name of the ComChannel of the EcuVariantGroup inside DVG must match with the known ComChannel identifier from OTX.

Attributes: AdvancedCheckerRule

Public Attributes