1. Introduction
1.1. About this document
This document is created to describe the test cases that can be executed using the OCPP Compliance Testing Tool (OCTT) for
OCPP 1.6.
1.2. Generic conventions
The following conventions / rules apply to all test cases, unless explicitly mentioned otherwise. These will not be mentioned
separately at every test case.
• All messages shall comply with the OCPP 1.6 schema’s.
• The messages are to be sent as mentioned in the scenario details except where noted otherwise.
• As an exception on the previous rule, StatusNotification(Charging) and StartTransaction.req may be reversed. This is also
the case for StatusNotification(Finishing) and StopTransaction.req.
• Manual actions and actions by external actors will be mentioned in the scenario details between [square brackets].
• When is asked to authenticate by presenting identification, this can be any form of identification. Pressing a start/stop
button for example is also allowed in this case.
• Validations will be mentioned and grouped per step.
• Not all test cases need to be passed to have successfully implemented OCPP 1.6. There are test cases which are optional
or conditionally optional.
• The tool will respond with a 4 call-error propertyConstraintViolation with errorcode: "correct payload, but value incorrect.".
When the payload contains an non-compliant value. This is not inline with the OCPP specification, but this message will only
be send after a test already failed.
• This document does not specify which tests need to be passed for certification, this will be specified in a separate
document.
1.3. General pre- and post conditions
Unless specifically noted otherwise. the following pre and post conditions apply:
• Central System is up and running
• Charge Point is Accepted by the Central System
• Charge Point has a stable active connection to the Central System
• Charge Point connectors are available
• Charge Point is Idle, with no active transactions
• Charge Point is clear of faults
• Charge Point has no charging schedules active
• Charge Point has no active reservations
• Charge Point has no installed local authorization list
• Charge Point has an empty authorization cache
• Charge Point has no more OCPP messages to be send in queue
• Charge Point is not busy with transfer of diagnostics
• Charge Point is not busy with download of firmware
• Charge Point is not upgrading firmware
• Charge Point is ready to accept/start a charging session
• MinimumStatusDuration should be set to 0. If the Charge Point does not support MinimumStatusDuration, the tests are still
able pass. The tool will display the 'unexpected' StatusNotification messages in a separate pop-up window. These need to
be manually validated by the tester.
OCPP Compliancy Testing Tool - TestCaseDocument Version 1.4.3
© Open Charge Alliance. 2022 2/164
