Test environment

The test environment is an essential part of the eMabler Charge Point Management System (CPMS) onboarding and configuration lifecycle. It replicates your production setup in a controlled, isolated environment, allowing you to test features, validate integrations, and simulate site behavior without affecting live operations. By using a dedicated sandbox, you minimize risks, accelerate troubleshooting, and ensure your EV charging platform is fully prepared before going live.

Why Use a Test Environment?

Using a test environment helps you ensure a smooth and error-free transition to production by enabling you to:

• Simulate complex charging scenarios
  Test various site structures, driver roles, access rights, and charging patterns.

• Test third-party integrations
  Validate your setup with hardware (chargers), OCPI endpoints, CRMs, ERPs, payment gateways, and more.

• Validate performance under different loads
  Identify bottlenecks, test responsiveness, and evaluate resilience.

• Ensure regulatory and business rule compliance
  Check tariff handling, transaction recording, and fallback behaviors to meet legal or business policies.

Setting Up a Test Environment with eMabler

Getting started with your own sandbox environment is simple and guided:

1. Request Access

• Contact your eMabler Customer Success Manager or reach out to support@emabler.com

• Mention your use case (e.g., OCPI integration, DLM testing, pricing simulation)

• Specify whether you'd like a dedicated tenant or a shared sandbox (based on your subscription)

2. Define Test Scope & Parameters

• Determine what aspects to test:

  • Site hierarchy (flat vs. nested)

  • Pricing models

  • API/webhook behavior

  • RFID/token scenarios

• Decide whether to simulate physical hardware or use backend stubs

3. Configure Infrastructure

• Mirror your intended production setup:

  • EVSEs (simulated or real test units)

  • Users & permissions

  • Site configurations

  • Charger profiles and commands

  • OCPI endpoint for handshake testing

4. Simulate Scenarios

• Conduct tests such as:

  • Charger authorization/denial logic

  • Scheduled charging windows

  • Load balancing (for DLM customers)

  • Interoperability with external platforms

5. Monitor & Iterate

• Use eMabler’s platform tools to:

  • Review logs and command history

  • Track site-level metrics and charger statuses

  • Troubleshoot through the admin dashboard

• Refine your configuration based on observed results

Best Practices

• Isolate credentials and tokens used in testing to avoid conflicts with live systems

• Document learnings from simulations and confirm configuration behaviors with your eMabler CSM

• Ensure your testing hardware is clearly labeled and not co-located with production units

Common Use Cases

Each use case helps you validate specific areas of your EV charging operations, making production rollout more reliable and predictable.