Software / Conformance Test Libraries
Conformance Test Libraries: From Requirement to Test Result
Choose repeatable charging tests for a defined device role, standard edition and software release. A Test Library specifies the starting conditions, action, expected response and evaluation for each included test case.
Which Test Library answers your test requirement?
Basis and scope
A published test plan does not establish library availability, and a test verdict does not automatically certify the DUT.
Text updated:
From requirement to repeatable result
A standard defines the requirement. The Test Library executes the verification.
A charging connector, communication interface or simulator creates access to the device under test. Conformance requires another layer: controlled preconditions, a defined sequence, observations, acceptance criteria, verdict logic and measurements linked to their test conditions.
Charging requirement
Standard, edition, amendment, profile, DUT role and referenced documents.
- What behaviour is required?
- Which implementation is in scope?
- Which conditions and exclusions apply?
Conformance Test Library
Implemented test logic that prepares, executes, observes, evaluates and documents.
- Preconditions and parameter sets
- Sequence and simulated counterpart
- Verdict and report logic
DUT evidence
A result that remains linked to the executed case, system setup and software versions.
- PASS, FAIL or inconclusive
- Trace, signal, timing and measurement context
- Repeatable regression asset
Physical access
The test interface answers: How is the DUT connected?
Connector, pilot signals, PLC (power line communication), CAN, measurement, power boundary, fault hardware and simulated EV or EVSE (electric vehicle supply equipment, or charging station) role.
Executable logic
The Test Library answers: How is the requirement verified?
Preconditions, sequence, parameters, observations, tolerances, verdict rules, reporting and released version support.
The controlled contract
One verdict needs one unambiguous library identity.
“ISO 15118 test” or “IEC 61851 test” is not a sufficient specification. Every released package and every result must state the complete contract.
Standard and edition
Base document, part, publication year, amendments, profile and referenced external specifications.
DUT role
EV, EVCC (vehicle-side charging communication controller), EVSE or SECC (station-side charging communication controller), simulated counterpart, charging direction and connector context.
Included cases
Named test cases, exclusions, capability declarations, preconditions and selectable parameters.
System configuration
EVCA path, interface modules, source or load, measurement devices, firmware, licences and the CANoe or comframe release required by the TestLib.
Evaluation and evidence
Observed values, timing windows, tolerances, verdict logic, trace links, report content and result status.
Release and support
Library version, validation status, release notes, compatibility, maintenance and application support.
Standard edition + DUT role + case ID + Test Library version + EVCA configuration + firmware + application software release + DUT buildSelect by DUT and released scope
Match the test family to its scope and software status.
Select the DUT role and test family, then check the software implementation alongside the required hardware. The ISO 15118-4/-5 SECC release in comframe is distinct from other TestLibs and their planned implementation. The quotation identifies exact editions, case sets, versions and licences.
CharIN Charging SystemBasic DC EVSE
Validated test-system capability for the published CharIN Basic DC EVSE application profile and approved setup.
- DUT
- DC EVSE
- Proof point
- CharIN provider listing
- Use
- Conformance and product-development testing within the stated profile
CharIN Charging SystemExtended DC EVSE
Validated test-system capability for the published CharIN Extended DC EVSE application profile and approved setup.
- DUT
- DC EVSE
- Proof point
- CharIN provider listing
- Use
- Extended profile testing within the approved system boundary
On smaller screens, scroll the table horizontally to see every column.
| Family or profile | Typical DUT role | Verification layer | Scope and hardware to specify | Software implementation and availability |
|---|---|---|---|---|
| IEC 61851-1AC charging control and electrical behaviour | EV or EVSE, depending on released package | Low-level signalling, states and electrical requirements | Portfolio route. Confirm edition, cases and configuration. | Confirm application software and release with the selected TestLib package. No family-wide comframe availability is implied. |
| SAE J1772 / NACSNorth American AC and DC interface route | EV or EVSE, depending on released package | Low-level signalling, communication and electrical behaviour within released scope | Portfolio route. Confirm connector, standard edition, DUT role and case set. | Confirm application software and release with the selected TestLib package. No family-wide comframe availability is implied. |
| IEC 61851-23DC EVSE tests, including Annex CC.7.5 | DC EVSE | Charging sequence, electrical behaviour, safety and fault-related scope | Annex CC.7.5 setup: EVCA Flex, IEC rack, switching and fault paths, source or load and measurement equipment matched to the agreed cases and operating limits. | Available: comemso IEC TestLib in CANoe; used in the customer demonstration. The port to comframe is prepared and is not yet released. |
| DIN SPEC 70121 / DIN SPEC 70122First-generation CCS communication | EVCC or SECC, depending on package | High-level communication conformance | Portfolio route. Confirm DUT direction and exact edition. | Confirm the current application with the selected package. Further CCS TestLibs in comframe are planned; see the roadmap below. |
| ISO 15118-2 with -4 / -5CCS communication conformance | EVCC or SECC, depending on package | Network and application behaviour within released scope | Confirm edition, included cases, role, security scope and EVCA configuration. The released comframe package covers ISO 15118-4/-5 SECC tests for AC and DC communication. | Released in comframe: ISO 15118-4/-5, SECC, AC and DC communication. Confirm EVCC packages separately; the SECC release does not establish their availability. |
| CHAdeMOVersion-specific charging communication | EV or EVSE, depending on package | Protocol and functional conformance | Portfolio route. Confirm association version and DUT role. | TestLibs implemented in firmware. Fully CANoe-independent application workflows are also planned; confirm the complete workflow for your package. |
| GB/T DCEdition-specific Chinese DC charging | EV or EVSE, depending on package | Protocol, states and electrical conformance | Portfolio route. Confirm standard edition and compatible interface. | DC-China / GB/T DC TestLibs implemented in firmware. Fully CANoe-independent application workflows are also planned; confirm the complete workflow for your package. |
Available scope: a standards-family listing does not confirm every test case, direction, edition or optional extension for every EVCA system. The quotation and release matrix define your project scope.
CharIN Conformance Test System
Validated test system. Defined profile. Clear boundary.
CharIN lists comemso as a validated Conformance Test System vendor for Charging System Basic and Charging System Extended DC EVSE. The validation is meaningful because it is profile-specific. The boundary must remain visible when the claim is used.
Open the official CharIN listingSystem capability for the stated profile
The approved test-system setup can execute the validated CharIN application-profile scope.
Every feature or future release
Optional EVCA functions, other standards, modified cases and later software versions are not automatically covered.
DUT certification or release responsibility
The tested product, responsible laboratory and applicable conformity scheme remain separate from test-system validation.
From project definition to regression
Execute the same controlled logic across development, validation and release.
The Test Library removes recurring test-programming work. Engineering effort remains focused on the DUT, the observed deviation and the release decision.
Select
Choose standard, edition, DUT role, interface, case scope and decision.
Configure
Load the released library, connect the approved hardware and record the DUT build.
Execute
Prepare preconditions, run the sequence and control the simulated counterpart.
Evaluate
Apply the defined acceptance logic and create an attributable verdict.
Diagnose
If a deviation occurs, open the protocol, signal, timing and electrical context at the first deviation.
Re-run
Preserve the case as a repeatable regression asset for the next build.
PASS/FAIL is the start of the decision
A failed test should lead to the cause, not another manual trace hunt.
Conformance evidence becomes more useful when the verdict is connected to the technical behaviour that created it. The available depth depends on the released library and system configuration.
Attributable identity
DUT build, case ID, library version, EVCA hardware, firmware, application software release and configuration.
Synchronised context
Decoded messages, protocol states, timing, pilot signals, CAN and electrical measurements where configured.
Transparent verdict
Expected behaviour, observed behaviour, acceptance limit and result linked to the active case.
Reusable regression
The released sequence and evidence structure can be repeated after firmware changes and across product variants.
ISO 15118-20 conformance route
Published test plans define the normative route. They do not announce a released library.
Second-generation conformance specifications now define common and DC-specific test plans for EVCC and SECC implementations of ISO 15118-20. Product availability remains a separate comemso release decision.
Both ISO specifications focus on communication capabilities and behaviour within their stated scope. They do not by themselves assess performance, robustness, reliability or the complete physical power path.
Define before quoting
Six inputs determine the correct Test Library path.
Start with the engineering decision. The product configuration follows from it.
- 1DUT and role
EV, EVCC, EVSE or SECC, including the simulated counterpart.
- 2Charging interface
AC, CCS, NACS, CHAdeMO, GB/T or MCS and the required connector path.
- 3Standard and edition
Exact parts, publication years, amendments, profile and security context.
- 4Required case scope
Communication, low-level signals, electrical behaviour, safety, faults or combined evidence.
- 5Power and measurement boundary
Communication-only, reduced power, full power, external source or load and metrology integration.
- 6Decision and evidence
Development, pre-compliance, validated profile, certification support or regression.
Official reference points
Verify profile status and normative editions at the source.
CharIN Conformance Testing
Current validated CCTS vendors and Charging System application profiles.
comemso EV Charging Tester
Publicly described charging standards, test-library families and EVCA configurations.
ISO 15118-21:2025
Published common conformance-test plan for ISO 15118-20 implementations.
Second generation, DCISO/PAS 15118-23:2026
Published DC-specific conformance-test plan for ISO 15118-20 implementations.
Frequently asked questions
Conformance Test Library FAQ
Use the answers to define the boundary. Use the released quotation, matrix and documentation to freeze the actual project scope.
What is a Conformance Test Library?
A Conformance Test Library is implemented, versioned and supported test logic for a defined standard, edition, DUT role and released scope. It prepares the test, controls the sequence, evaluates observations and preserves the result with its technical evidence.
How is a Test Library different from a charging interface?
The charging interface provides physical and communication access to the DUT. The Test Library adds preconditions, parameter sets, sequence control, observations, verdict rules, report content and version control for a defined conformance scope.
Does a PASS verdict mean that the DUT is certified?
Not automatically. A PASS verdict applies to the executed cases, configuration and versions recorded in the result. Formal product certification or a Supplier Declaration of Conformity can require a defined scheme, an approved laboratory and additional evidence.
What does CharIN CCTS validation prove?
CharIN validation confirms the test-system capability for the stated Charging System application profile and approved setup. It does not validate every EVCA function, every optional library, every later software release or the customer DUT.
Can conformance test cases be modified?
Depending on the released package, parameters or engineering copies can be adapted for development work. Once normative logic or acceptance criteria are changed, the result must be identified as an engineering test rather than an unchanged formal conformance case.
Can one library test both EV and EVSE roles?
Only when the released package explicitly includes both directions. EVCC and SECC testing use different simulated counterparts, preconditions and expected behaviour. DUT role is part of the library identity.
Defined conformance scope
Connect the applicable document to executable evidence.
Specify standard, edition, DUT role, released Test Library and required report.