Skip to content
Features

OCPP & OCPI Testing Features

Everything you need to test OCPP 1.6, OCPP 2.0.1, OCPI 2.1.1, and OCPI 2.2.1 at production scale, from protocol simulation to repeatable QA workflows.

OCPP 1.6 & 2.0.1 Protocol Support

Test OCPP 1.6 and OCPP 2.0.1 workflows from one browser workspace. Strict validation helps teams catch message-shape issues before they reach production systems.

  • Core OCPP 1.6 flows such as BootNotification, StartTransaction, and MeterValues
  • OCPP 2.0.1 flows including device-management and certificate-oriented scenarios
  • Protocol-version setup for OCPP 1.6 and OCPP 2.0.1 test runs
  • JSON schema validation on every message exchange

OCPI 2.1.1 & 2.2.1 Roaming Coverage

Test CPO-eMSP roaming workflows, OCPI hub-style integration paths, and cross-platform interoperability across OCPI 2.1.1 and OCPI 2.2.1 without needing real roaming partners.

  • Simulate CPO and eMSP endpoints for bilateral OCPI 2.1.1 and 2.2.1 testing
  • Hub-oriented compatibility testing with reusable flows
  • Token authorization, CDR exchange, and tariff sync validation across both versions
  • ChargingProfiles and HubClientInfo coverage for OCPI 2.2.1 workflows

Workflow-Based Test Automation

Build repeatable OCPP and OCPI test workflows, edit them visually, and run them continuously as your integration changes.

  • Reusable scenario templates for OCPP/OCPI flows
  • Regression workflows for common edge cases
  • Visual workflow editor for repeatable release checks
  • Automation hooks and webhooks for recurring release checks

Load Testing & Stress Testing

Run high-volume virtual charge point tests to find CPMS bottlenecks before customers do.

  • Exercise many concurrent OCPP WebSocket connections
  • Realistic charging session patterns with configurable behavior
  • Performance metrics: latency, throughput, error rates
  • Identify bottlenecks in connection handling, message processing, and database writes

WebSocket Debugging & Protocol Inspector

Real-time message inspection with full request/response logging. Filter, search, and replay any OCPP message exchange.

  • Live WebSocket message stream with syntax highlighting
  • Message filtering by type, charge point, or time range
  • Request/response correlation and latency tracking
  • Share replayable message traces for offline analysis

Security-Focused Protocol Evidence

Check TLS, authentication flows, and OCPP security-profile behavior. Share protocol traces for internal release and procurement reviews.

  • OCPP Security Profile 1, 2, and 3 testing
  • TLS certificate validation and cipher suite checks
  • Authentication flow testing (Basic Auth, client certificates)
  • Replayable traces for reviewers

Feature coverage summary

OCPPLab provides six core capabilities for EV charging infrastructure testing. These are: (1) OCPP 1.6 and OCPP 2.0.1 protocol simulation with JSON schema validation, (2) OCPI 2.1.1 and OCPI 2.2.1 roaming and interoperability testing including hub-oriented workflows, ChargingProfiles, and HubClientInfo coverage, (3) reusable QA workflows for common protocol edge cases. It also includes (4) high-volume load testing for concurrent WebSocket connections, (5) real-time WebSocket message debugging with filtering, replay, and shareable traces, and (6) protocol evidence for release and procurement reviews.

Supported vendor and partner coverage

Teams usually need proof that the product can support both protocol versions and the vendor or roaming contexts that show up in real projects.

AreaCoverageTypical proof path
OCPP protocol coverageOCPP 1.6 and OCPP 2.0.1Transactions, status flows, smart charging, security profiles, and device-model behavior.
OCPI roaming coverageOCPI 2.1.1 and OCPI 2.2.1Credentials, locations, sessions, CDRs, tariffs, ChargingProfiles, and hub-oriented workflows.
Vendor-oriented testingABB, EVBox, Wallbox, Alfen, and mixed-fleet profilesUse vendor-specific integration pages and CPMS regression flows to validate compatibility before rollout.
Partner and hub validationOCPI hub-style, Hubject-facing, and direct CPO/eMSP roaming pathsValidate onboarding, hub-mediated flows, and partner-readiness before certification or go-live.
Representative scenarios

Two evaluations buyers run before they sign.

Two example paths buyers run during a typical evaluation. Use them as a checklist for what to verify in the trial, not as customer case studies.

Scenario 01

CPMS release team

Mixed-fleet OCPP regression before production rollout

Your backend team needs proof that a CPMS release will not break charger onboarding, transactions, or smart charging on the legacy fleet or the new one.

What they usually verify

  • Run OCPP 1.6 and OCPP 2.0.1 chargers side by side. ABB, EVBox, Wallbox, and Alfen-style profiles in the same workspace.
  • Replay BootNotification, Authorize, MeterValues, TransactionEvent, reconnect, and remote-command flows. Inspect raw protocol logs as they happen.
  • Decide whether Starter, Pro, or Enterprise matches your charger volume, automation depth, and deployment needs.

Scenario 02

Roaming interoperability team

OCPI partner onboarding before hub or bilateral go-live

Your roaming team validates credentials, tariffs, sessions, and CDR exchanges before a new OCPI connection touches a real partner or a certification path.

What they usually verify

  • Exercise credentials, locations, tokens, sessions, CDRs, and tariff sync. OCPI 2.1.1 and 2.2.1 in one workspace.
  • Rehearse hub paths: GIREVE, Hubject, ChargingProfiles, HubClientInfo. Direct or via a hub.
  • Confirm in the first demo whether OCPPLab fits direct partner validation, certification prep, or wider roaming regression testing.

Ready to test your CPMS?

Deploy your first virtual charge point in 2 minutes. No credit card required.

Last updated: