tux-evse/injector-binding-rs

Injects AFB RPCs into afb-v4 binding API/VERB and check expected result

injector-binding-rs inject RPC request into afb-v4 framework

This injector initial objective addresses ISO15118/OCPP simulation for charger and/or electric vehicle. Nevertheless nothing is specific to EV/EVSE and it may test/simulates any API based on Afb-V4 framework.

The injector/simulator implements one api/verb per configure scenario. At the end of the test it return a normalized TAP response, that hopefully should integrated easily within any CI/CD model.

Dependencies

• serde
• serde_json

optional Dependencies

• afbv4

'afb-librust' should be install on your system.

/usr/lib/rustlib/%{_arch}-unknown-linux-gnu/lib/libafbv4.rlib

For development purpose, you can use an external libafbv4. To activate it, as a feature, you can execute:

cargo add --git https://github.com/redpesk-common/afb-librust afbv4 --optional

And build with the features "afbv4"

cargo build --features afbv4

You can also directly edit the file Cargo.toml, and manually change it.

Configuration

Configuration relies on standard binding/binder json/yaml config file. The injector create a new verb per scenario. When executing a scenario, client receives an event per action. At the end of the test client may request scenario global status that is then return as Json/TAP.

Scenario metadata should define:

• uid: which define the api/verb to start/stop/check the execution
• info: a simple free comment
• target: the API to be tested. Depending on config, this might be local or remote API.

    scenarios:
      - uid: scenario-1
        info: simple iso2 connection scenario
        target: iso2
        transactions:

Scenarion transactions should defined:

• uid: test name
• verb: injector call $target/$test (when not defined: derives from UID as: uid-sample->uid_sample_req)
• delay: wait in ms before starting the test
• query: param value to be added to test/api/verb
• response: optional expected response (test only defined values). When not defined injector relies on RPC status to set OK/FX test result.

        transactions:
        - uid: sdp-evse
          query:
            action: discover
        - uid: iso2-handshake
          verb: app_proto_req

Note: scenario/start verb does not wait the end of the scenario to return. This because a scenario may last longueur than browser typical timeout.

starting the injector

Technically the injector is only "yet an other binding". The simplest way to start it is to add it configuration as the end of the binding to be tested.

Note: by default the API to be tested remain visible from "devtools", to remove it simply pass the binding to be tested in 'private' mode.

afb-binder -v \
   --config=$ROOTDIR/iso15118-2/etc/binding-iso-2.yaml \
   --config=$CONFDIR/binding-simulator.yaml \
   $*

For further information on config: https://docs.redpesk.bzh/docs/en/master/developer-guides/resource-bindings.html#using-a-resource-binding-with-a-config