Capture library

Files with a known outcome, made by test stacks for one scenario each and checked before they are published: download them or open them in the analyzer.

What is in it

  • Each entry is one scenario: what it is set to do, the result it promises, the files, and the generator that made them with its version.
  • OCPP logs for 1.6, 2.0.1 and 2.1: the charge point emulator plays a charging session and a reconnect against the OCPP sandbox. These come out the same byte for byte each time they are made.
  • V2G captures come from Josev, the open source ISO 15118 stack of SwitchEV: its car and its charger run in two network namespaces in GitHub Actions and are captured on the link between them. A capture is added once its run has passed the checks below.

How every file is checked

  • The label comes from the scenario, before the file exists. A capture has to get exactly that verdict from the analyzer; an OCPP log has to hold the promised transactions with every message inside the schema of its version.
  • The secret scan refuses a private key in PEM or DER, a certificate that is not one of the test PKI made for that run, a card id that is not a test token, and a MAC address a manufacturer assigned (the stacks run with locally administered ones).
  • Every file carries its SHA-256 and size; nothing is published that the manifest does not list. CI runs these checks on every push (scripts/library/verify.ts).

Use it

  • On the public site, Capture library lists every entry with its files to download.
  • In the hosted analyzer, Library opens a capture with its key log in one step. An OCPP log joins the capture that is open, or opens in Batch for the OCPP checks and the ChargeX KPIs.
  • The command line runner reads the same files: v2g-analyze with a capture from the library gives the verdict of its label.