Open Test Framework - Access Path

From emotive
Jump to: navigation, search


Access path is a solid connection from OTX to ODX data. It comprises the shortnames of following ODX element: logical link, ecuvariant (optional), diagservice, request/response and parameter, written in order and separated with ".".

An example of complete access path: "LL_AccesStartInterUDS.EV_KessyHellaMQBAB_002.DiagnServi_ReadDataByIdentActuaTestStatu.Req_ReadDataByIdentActuaTestStatu.Param_RequeServiId"

Access path can be determined from the workflow via shortnames of property of term/action like GetComChannel, CreateDiagServiceByName or ExecuteDiagService. In some cases, access path can just be detected at runtime. Thereby it would be set at the AccessPath property of corresponding actions.


Both determined and set access path will be validated in OTF. There 3 check rules for access path:

  • DiagCom_Chk100 (warning): The access path can not be determined unambiguously. For example: the ODX database is not set yet.
  • DiagCom_Chk101 (critical): The access path may be determined, but the target does not exist (in the ODX database).
  • DiagCom_Chk102 (warning): The objectives of the access paths exist, but do not have the same structure (attributes).

In validation, the values ​​in AccessPath property are used only when the access path can not be explicitly determined from the workflow.

Access path validation

Shortname selection

Access path is also used to find all the possible values of shortname for property of ComChannel, DiagService or Request/Response parameters. When opening the properties, users just has to choose the right value instead of seeking and entering it themselves.

Shortname selection