Release Testing

This page intends to list the tests that we shall/must do before we do a release for this repository. The intention of the release test is to do a reasonable regression test for components listed as Beta/Production/Stable/Mature in the KUKSA Component Maturity Overview. It is assumed that new features of individual components have been thoroughly tested, the focus of the release test is to verify that there are no regressions. For capacity reasons the tests have no intention to cover all possible use cases.

Prerequisites

• No outstanding Pull Requests that may affect component behavior.
• CI Docker builds on latest master has succeeded
• Pre-release of kuksa-client exists on PyPI

Tests

Basic functionality, TLS and Tokens

Verify that reading and writing Vehicle.Speed works for the following combinations

Abbreviations

• DB = Databroker
• S = Server
• TOK = JWT Tokens
• TLS = TLS
• D = DOCKER (If not mantioned native shall be used)
• DBC = Databroker Client
• PC = Python Client
• GC = Go Client

Left of "equal" denotes Server, right of "equal" denotes client side "Minus" used to separate parts

Databroker (Insecure, No TLS)

erik@debian3:~/kuksa.val/kuksa_databroker$ cargo run --bin databroker -- --metadata ../data/vss-core/vss_release_4.0.json --insecure

Python Client test

(kuksa-client) erik@debian3:~/kuksa.val/kuksa-client$ kuksa-client --ip 127.0.0.1 --port 55555 --protocol grpc  --insecure


Test Client> setValue Vehicle.Speed 33
OK

Test Client> getValue Vehicle.Speed

Databroker CLI

erik@debian3:~/kuksa.val/kuksa_databroker$ cargo run --bin databroker-cli
...
sdv.databroker.v1 > feed Vehicle.Speed 44
[feed]  OK  
sdv.databroker.v1 > get Vehicle.Speed
[get]  OK  
Vehicle.Speed: 44.00

• DB-TOK=PC
• DB-TLS=PC
• DB-TOK-TLS-D=PC-D
• DB-TOK-TLS=DBC
• DB=DBC-D
• DB=GC
• DBC