Skip to main content
Log inSign up

The fastest way to know whether your OCPP 1.6 implementation will survive certification

Automated test suites catch protocol failures in minutes, not weeks, so teams ship interoperable products with significantly less certification risk.

Start testing

The problem

Getting an OCPP 1.6 implementation right is harder than the spec makes it look. Teams today face a narrow set of options, each with real gaps.

OCTT requires hardware and expertise

OCA’s OCPP Compliance Testing Tool is thorough and authoritative — but it requires a license, dedicated hardware setup, and hands-on expertise. Most teams only run it late in the cycle, when failures are expensive to fix.

Lab testing runs on lab timelines

Formal certification through DEKRA, TÜV, and other labs operates on lab timelines and lab budgets. A single round can take weeks and cost tens of thousands of dollars. Iteration loops are measured in months, not days.

Ad-hoc testing leaves gaps

Engineers write one-off scripts, manually replay WebSocket traces, and hope they’ve covered enough of the spec. There is no structured coverage, no repeatable baseline, and no clear signal of readiness.

Our approach

TestChargePoint sits between internal ad-hoc testing and formal certification. A SaaS platform that runs structured, automated OCPP 1.6 test suites against your implementation and tells you exactly what passed, what failed, and why.

  1. Structured test coverage. Test suites organized around OCPP 1.6 protocol areas — authorization, transactions, firmware, diagnostics, smart charging — not around guesswork.
  2. Readable failure diagnostics. Every failed test produces a clear explanation at the message level: which PDU was wrong, which field was unexpected, what the spec requires.
  3. Repeatable runs. The same suite produces the same results every time. Run it after every code change, before every release. Build a history of pass/fail over time.
  4. Both sides of the wire. Test your charge point against our simulated CSMS, or test your CSMS against our simulated charge point. Same platform, same workflow.
  5. No hardware required. Connect over WebSocket. Run from anywhere. No lab, no dedicated test bench, no scheduling.

Who it's for

Charger OEMs

You need to know — before you ship hardware to a certification lab — whether your firmware handles OCPP correctly. TestChargePoint gives your team a fast, repeatable way to validate protocol behavior and catch regressions between releases.

CSMS Vendors

Interoperability failures surface in the field as customer complaints. Validate CSMS-side protocol handling against a structured test suite, reducing the risk of field failures and increasing confidence before customer deployments.

System Integrators

You are assembling solutions from multiple vendors and you are on the hook when they don’t work together. Get an independent way to validate each side’s OCPP 1.6 compliance before you put them on a site together.

What we're not

Honesty about boundaries matters more than overreach. Think of TestChargePoint as the practice exams before the real test.

  • We are not a certification body. Only OCA-authorized processes can issue OCPP compliance certificates.
  • We are not a replacement for OCTT. OCTT is the definitive tool for formal certification testing. We help teams prepare for that step, not skip it.
  • We are not a replacement for lab testing. If your market requires formal certification from DEKRA or TÜV, you still need that process.
  • We do not guarantee certification outcomes. We increase the likelihood of passing by catching failures earlier. We reduce risk; we do not eliminate it.

Key differentiators

  1. Pre-certification readiness in minutes, not weeks. Run a full OCPP 1.6 test suite against your implementation and get results the same day, not after a multi-week lab engagement.
  2. Message-level failure diagnostics. Every test failure includes the exact PDU exchange, the specific field or value that was incorrect, and a reference to what the specification requires.
  3. Both charger-side and CSMS-side testing. One platform covers both directions of the protocol. No need for separate tools or separate workflows.
  4. Repeatable, deterministic test runs. Same inputs, same assertions, same results. Suitable for regression testing across firmware versions, CSMS releases, or configuration changes.
  5. No hardware, no lab, no scheduling. Pure software, WebSocket-based. Your implementation connects to TestChargePoint from any network-accessible environment.
  6. Developer-first experience. Designed for engineers, not compliance managers. Clear test names, readable output, fast feedback. Built to fit into a development workflow.
  7. Lower barrier to quality. Teams that cannot yet justify OCTT licensing or lab budgets still get structured protocol validation. Quality testing should not be gated by budget alone.

Ready to validate your implementation?

Start testing your chargers and CSMS against the OCPP specification today.

Start Testing