EVSE Test Plan Checklist for Engineering Teams

Document scope and configuration

Identify the charger model, hardware and software versions, connector, AC or DC rating and target market. List the exact standards and customer requirements in scope. Record the tester, cables, adapters, external load, programmable sources and measurement instruments needed for each configuration.

Define environmental and facility assumptions such as supply limits, grounding, network access and the permitted energy path. Mark exclusions clearly. A test plan is more useful when it states what will not be verified than when it uses broad language that cannot be tied to evidence.

• ✓ Identify hardware and software versions
• ✓ List standards and customer requirements
• ✓ Record instruments, fixtures and exclusions

Write measurable test cases

Each case should state its initial charger condition, connection state, parameter settings, operator or automated action, expected response and acceptance limits. Separate normal charging, boundary values, communication behavior, metering checks and safety faults so a failure has a clear source.

Include timing where sequence behavior matters. Specify which messages, waveforms, measured values, screenshots or reports must be retained. Use stable case identifiers that appear in both the procedure and result export, allowing findings to be traced without manually matching descriptions.

Review execution and change control

Run a small pilot set before the full campaign to identify ambiguous instructions, unavailable ranges and missing evidence. Require reviewers to check both the result and the supporting record. When charger firmware, tester software or a procedure changes, record the revision and decide which cases must be repeated rather than silently combining incompatible results.

• ✓ Pilot representative normal and fault cases
• ✓ Review evidence with results
• ✓ Version procedures and rerun affected cases