The ChargeX EV-EVSE Interoperability Test Plan

What the EEITP of the ChargeX Consortium is (version 2.0, July 2025, maintained by Argonne), how its test cases are organised and described, the Navigator app that browses them, and how it relates to the worked test cases of this tool.

What it is

The EV-EVSE Interoperability Test Plan (EEITP) was written by the testing task force of the ChargeX Consortium, with researchers from Argonne, Idaho and the National Renewable Energy Laboratory. It aims at a common way to test whether a car and a charger work together, drawing on ISO, SAE, OCPP and related standards. Version 1.0 came first; version 2.0 was released in July 2025, and Argonne maintains it as a living document.

Version 1 drew on three internal test plans from industry, review by seven experts, four inputs from a ChargeX survey and a workshop. The procedures were tried out and refined at CharIN North America Testivals in the ChargeX prescribed testing program (Interoperability test events, CharIN Testivals and the first public test data).

How it is organised

Version 2.0 holds 118 detailed test cases, some with several variants, in 17 test types under three categories. The workbook states that the test cases cover 17 of the 26 ChargeX Minimum Required Error Codes (MRECs).

CategoryTest types (number of test cases)
Baseline functionality and safetyAuthentication types, methods and timeouts (16); idle error faults, EVSE only (5); power transfer (19); session initialization, from authentication to power transfer (8)
Advanced chargingAdapters (3); charge discovery protocol (4); dynamic bidirectional power transfer (3); OCPP smart charge profile (7); pause and resume (4); pilot wake (3); scheduled bidirectional power transfer (1); seamless retry (10); simultaneous charging from one dispenser (4); smart charge scheduling (10)
Single PKIBasic certificate validity (6); revocation of EVSE and contract certificates (9); revocation of Sub-CA 2 certificates (6)

The fields of a test case

FieldWhat it holds
NrThe test case number
Test Category and Test TypeWhere the case sits in the tree above
Test Name and PurposeWhat is tested and why
Test ConditionsWhat must be set up before the steps: vehicle state, authentication type, protocol, certificates and so on; variants are numbered here
StepsThe actions, in order
Pass CriteriaWhat must happen for a pass, per variant
Observed MetricsWhat to record while running the case
Intended MRECs and Other Possible MRECsThe error codes the charger should report when the case provokes a fault, and others it may report
Applicable OSI LayerThe layer the case exercises
Repeatability requirementWhether the result must be repeated to count (yes for 75 cases, no for 43)
Estimated DurationPlanning time for the case
Electrical Safety LevelThe safety precaution the case needs: an electrically safe work condition for most (108), lock-out, tag-out and zero voltage verification for 10
Test Case NotesRemarks

The same structure appears in a PDF with one table per test case and in a Word template for recording results.

The Navigator app

  • The ChargeX-ITP Navigator is a standalone Windows program: a tree of categories, types and test cases on the left, the test table of the chosen case on the right, ready to print.
  • It is built from the Excel workbook: a Python script turns each row into an HTML test table, a small Flask server and a JavaScript tree serve them, and PyInstaller packs everything into one executable. The builder scripts are in the repository, so an updated workbook can be turned into a new Navigator.
  • Windows may block the downloaded executable; the README explains how to unblock it.

The repository also holds the three reports of the ChargeX prescribed testing program at CharIN Testivals (June 2024, November 2024 and May 2025).

How it relates to the test cases in this tool

The EEITP repository has no licence file; its README calls the plan an open source deliverable of ChargeX. This page therefore describes and links the plan and does not reproduce its test cases. Ask Argonne before copying them.

Sources