Skip to content
Documentation Menu

TC_B_11_CS — Set Variables - invalidly formatted values

TC_B_11_CS — Set Variables - invalidly formatted values

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block B. Provisioning, page 44.

Identification

FieldValue
Test case nameSet Variables - invalidly formatted values
Test case IdTC_B_11_CS
Use case Id(s)B05
Requirement(s)B05.FR.07
System under testCharging Station
Functional blockB. Provisioning

Description

Set the value of two of the required variables of OCPPCommCtrlr

Purpose

To test setting of variables of different type with invalidly formatted values using GetVariablesRequest for one of the mandatory component/variable combinations that must exist in the DM implementation.

Prerequisite(s)

Charging Station DM has the variable "NextTimeOffsetTransitionDateTime" of component "ClockCtrlr" to test setting of a date.

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
Notes: Steps 1 to 8 are repeated 5 times for value = 1, 1.1, true, currentTime, "abc"
2. Charging Station responds with SetVariablesResponse with If component/variable/value not supported: attributeStatus = Rejected attributeStatusInfo = InvalidValue If component/variable/value supported: attributeStatus = Accepted1. OCTT sends SetVariablesRequest with; - variable.name = "OfflineThreshold"; - component.name = "OCPPCommCtrlr"; - attributeValue = value
4. Charging Station responds with SetVariablesResponse with If component/variable/value not supported: attributeStatus = Rejected attributeStatusInfo = InvalidValue If component/variable/value supported: attributeStatus = Accepted3. OCTT sends SetVariablesRequest with; - variable.name = "LimitChangeSignificance"; - component.name = "SmartChargingCtrlr"; - attributeValue = value
Notes: Steps 5 and 6 will only be executed if this component/variable combination is readwrite
6. Charging Station responds with SetVariablesResponse with If component/variable/value not supported: attributeStatus = Rejected attributeStatusInfo = InvalidValue If component/variable/value supported: attributeStatus = Accepted5. OCTT sends SetVariablesRequest with:; - variable.name = "AuthorizeRemoteStart"; - component.name = "AuthCtrlr"; - attributeValue = value
Notes: Steps 7 and 8 will only be executed if the CS supports this component/variable combination
8. Charging Station responds with SetVariablesResponse with If component/variable/value not supported: attributeStatus = Rejected attributeStatusInfo = InvalidValue If component/variable/value supported: attributeStatus = Accepted7. OCTT sends SetVariablesRequest with:; - variable.name = "NextTimeOffsetTransitionDateTime"; - component.name = "ClockCtrlr"; - attributeValue = value

Tool validations

Step 2:

Message: SetVariablesResponse has SetVariableResultType

  • attributeStatus = Rejected/Accepted
  • attributeType = Actual
  • component.name = "OCPPCommCtrlr"
  • variable.name = "OfflineThreshold"
  • attributeStatusInfo is absent or attributeStatusInfo.reasonCode = InvalidValue (not required)

Step 4:

Message: SetVariablesResponse has SetVariableResultType

  • attributeStatus = Rejected/Accepted
  • attributeType = Actual
  • component.name = "AuthCtrlr"
  • variable.name = "AuthorizeRemoteStart"
  • attributeStatusInfo is absent or attributeStatusInfo.reasonCode = InvalidValue (not required)

Step 6:

Message: SetVariablesResponse has SetVariableResultType

  • attributeStatus = Rejected/Accepted
  • attributeType = Actual
  • component.name = "SmartChargingCtrlr"
  • variable.name = "LimitChangeSignificance"
  • attributeStatusInfo is absent or attributeStatusInfo.reasonCode = InvalidValue (not required)

Step 8:

Message: SetVariablesResponse has SetVariableResultType

  • attributeStatus = Rejected/Accepted
  • attributeType = Actual
  • component.name = "ClockCtrlr"
  • variable.name = "NextTimeOffsetTransitionDateTime"
  • attributeStatusInfo is absent or attributeStatusInfo.reasonCode = InvalidValue (not required)

Post scenario validations

  • N/a