Release Testing

See also kuksa.val release testing

Prerequisites

• Kuksa-client PyPI package released
• All feeders/providers updated to use new kuksa-client release
• Running latest released Broker/Server as needed

Databroker (TLS; Token)

erik@debian3:~/kuksa.val/kuksa_databroker$ cargo run --bin databroker -- --metadata ../data/vss-core/vss_release_4.0.json --tls-cert ../kuksa_certificates/Server.pem --tls-private-key ../kuksa_certificates/Server.key --jwt-public-key ../kuksa_certificates/jwt/jwt.key.pub

DDS Provider

TBD

Databroker (TLS; no token)

erik@debian3:~/kuksa.val/kuksa_databroker$ cargo run --bin databroker -- --metadata ../data/vss-core/vss_release_4.0.json --tls-cert ../kuksa_certificates/Server.pem --tls-private-key ../kuksa_certificates/Server.key

DDS-provider

Test basically as described in https://github.com/eclipse-kuksa/kuksa-dds-provider/blob/main/README.md

Start KML Replay. Start DDS Feeder

erik@debian3:~/kuksa.val.feeders/dds2val$ VDB_ROOT_CA_PATH=/home/erik/kuksa.val/kuksa_certificates/CA.pem VDB_TLS_SERVER_NAME=Server python3 ddsprovider.py

Verify with client that latitude updates frequently

Test Client> getValue Vehicle.CurrentLocation.Latitude
{
    "path": "Vehicle.CurrentLocation.Latitude",
    "value": {
        "value": 9.90499,
        "timestamp": "2023-07-26T11:42:48.513418+00:00"
    }
}