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 AI-powered QA automation.

OCPPLab provides six core capabilities for EV charging infrastructure testing: (1) full 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 GIREVE hub compatibility, ChargingProfiles, and HubClientInfo coverage, (3) AI-powered test automation that generates test cases from natural language descriptions, (4) load testing with 10,000+ concurrent WebSocket connections, (5) real-time WebSocket message debugging with filtering, replay, and export, and (6) automated compliance auditing for OCPP Security Profiles 1-3 with SOC2 and ISO 27001 exportable reports.

OCPP 1.6 & 2.0.1 Protocol Support

Complete implementation of both OCPP versions with full message coverage. Switch between OCPP 1.6 and OCPP 2.0.1 workflows with one click while strict validation ensures every message conforms to the specification.

  • All OCPP 1.6 messages supported (BootNotification, StartTransaction, MeterValues, etc.)
  • Full OCPP 2.0.1 support including device management and ISO 15118
  • Automatic protocol version detection and negotiation
  • JSON schema validation on every message exchange

OCPI 2.1.1 & 2.2.1 Roaming Coverage

Test CPO-eMSP roaming workflows, GIREVE hub integration, 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
  • GIREVE and hub-oriented compatibility testing with pre-built flows
  • Token authorization, CDR exchange, and tariff sync validation across both versions
  • ChargingProfiles and HubClientInfo coverage for OCPI 2.2.1 workflows

AI-Powered Test Automation

Describe your test scenario in plain English and let our AI generate the workflow, edge cases, and assertions. Edit visually, run continuously.

  • Natural language test generation for OCPP/OCPI flows
  • Automatic edge case discovery and regression testing
  • Visual test editor with drag-and-drop workflow builder
  • 24/7 automated test execution with Slack/email alerts

Load Testing & Stress Testing

Spin up 10,000+ virtual charge points simultaneously to find breaking points in your CSMS before your customers do.

  • Simulate 10,000+ concurrent 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
  • Export message logs for offline analysis

Compliance & Security Auditing

Automated TLS/SSL checks, authentication flow testing, and OCPP Security Profile 3 compliance. Export audit-ready reports for SOC2 and ISO 27001.

  • OCPP Security Profile 1, 2, and 3 testing
  • TLS certificate validation and cipher suite checks
  • Authentication flow testing (Basic Auth, client certificates)
  • Exportable compliance reports for auditors

Proof in product

The platform is not just a landing page promise. These screens show the kinds of operational views teams use when they validate protocol traffic, build workflows, and manage virtual charger coverage.

OCPPLab protocol log viewer showing OCPP and OCPI message traces

Real-time protocol logs

Inspect request and response traffic with timing, message details, and the context QA teams need during protocol debugging.

OCPPLab workflow builder for OCPP and OCPI test scenarios

Workflow builder

Build or edit test flows visually instead of stitching every scenario together by hand in code or spreadsheets.

OCPPLab charger model and profile coverage interface

Device and profile coverage

Choose from virtual charger profiles and coverage views that make mixed-fleet testing easier to manage and repeat.

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 CSMS regression flows to validate compatibility before rollout.
Partner and hub validationGIREVE, Hubject, direct CPO/eMSP roaming pathsValidate onboarding, hub-mediated flows, and partner-readiness before certification or go-live.

Representative Scenarios

Two ways teams usually prove fit before they buy

These are representative evaluation paths based on the kinds of OCPP and OCPI workflows teams need to validate. They are examples of how buyers usually inspect product fit, not named customer case studies.

Representative scenario 01

CSMS release team

Mixed-fleet OCPP regression before a production rollout

A backend team wants confidence that a CSMS release will not break charger onboarding, transactions, or smart charging across both legacy and newer fleets.

What they usually verify

  • Run OCPP 1.6 and OCPP 2.0.1 chargers side by side with ABB, EVBox, Wallbox, and Alfen-style profiles.
  • Replay BootNotification, Authorize, MeterValues, TransactionEvent, reconnect, and remote-command flows while inspecting raw protocol logs.
  • Use the evaluation to decide whether the Developer, Professional, or Enterprise plan matches charger volume, automation depth, and deployment needs.

Representative scenario 02

Roaming interoperability team

OCPI partner onboarding before hub or bilateral go-live

A roaming team needs to validate credentials, tariffs, sessions, and CDR exchanges before a new OCPI connection reaches a real partner or certification path.

What they usually verify

  • Exercise credentials, locations, tokens, sessions, CDRs, and tariff sync flows across OCPI 2.1.1 and OCPI 2.2.1.
  • Rehearse hub-oriented paths such as GIREVE, Hubject, ChargingProfiles, and HubClientInfo handling where relevant.
  • Use the first demo to confirm whether OCPPLab fits direct partner validation, certification prep, or wider roaming regression testing.

Ready to test your CSMS?

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

Last updated: