OCPP and OCPI testing scenarios
Run virtual chargers on OCPP 1.6, 2.0.1 and 2.1 against your CSMS before a release. Connect up to 100 of them at once to see which OCPP actions slow down. Bring up an OCPI connection against an OCPPLab counterparty before a real partner sees it.
Example list of test runs with a passed OCPP 2.0.1 run expanded to its checks: BootNotification, StatusNotification, SetChargingProfile. CSMS testing
Test your Charging Station Management System against virtual charge points. Run OCPP 1.6 / 2.0.1 / 2.1 chargers in one test run, see each failed check with its frame and error code, and automate release checks.
Vendor-style profiles1.6 · 2.0.1 · 2.1 in one runCALLERROR on its own rowExample load-run ramp to 100 virtual chargers with one p95 latency row for MeterValues and no value; shape only, no measured values. OCPP load testing
Run one OCPP workflow on up to 100 virtual chargers at once, for up to 10 minutes. Find weak points in WebSocket handling, message processing, and database writes under concurrent load.
Up to 100 chargersp95 latency per actionCheck pass rateExample: your CPO platform and an OCPPLab eMSP counterparty, marked Connected, with the two requests between them: GET /versions and POST /credentials. OCPI roaming testing
Test OCPI 2.1.1 / 2.2.1 / 2.3.0 roaming workflows between CPOs and eMSPs without real partners. Validate GIREVE hub integration, token authorization, CDR exchange, hub modules, Bookings, and location data sync.
CPO & eMSP simulationGIREVE hub testingCDR reconciliation
Need a workflow not listed?
Send us the OCPP or OCPI frames you want to test.