forked from eclipse-kuksa/kuksa-databroker
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathviss_v2_multiple_paths.feature
38 lines (32 loc) · 1.56 KB
/
viss_v2_multiple_paths.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
#
# https://w3c.github.io/automotive/spec/VISSv2_Core.html#read
#
Feature: VISS v2 Compliance Testing - Multiple Paths
Background:
Given the VISS server is running
Given the VISS client is connected via WebSocket
# 5.1.2 Read request - Single value request
# The VISS server must support reading a single value from a valid data path.
@MustHave
Scenario: Request for a single value from a single node
When I send a read request with path "Vehicle.Speed"
Then I should receive a single value from a single node
# 5.1.2 Read request - Multiple values from a single node
# The VISS server should support reading multiple values from a single data node.
@ShouldHave
Scenario: Request for multiple values from a single node
# This scenario can be expanded based on specific use cases.
When I search "Vehicle.Cabin" using a path filter "Door.*.*.IsOpen"
Then I should receive multiple data points
# 5.1.2 Read request - Single value request from multiple nodes
# The VISS server must support reading values from multiple nodes using path filters.
@MustHave
Scenario: Request for a single value from multiple nodes
When I search "Vehicle" using a path filter "*"
Then I should receive multiple data points
# 5.1.2 Read request - Multiple values from multiple nodes
# The VISS server should support reading multiple values from multiple nodes.
@ShouldHave
Scenario: Path request for multiple values must not contain any wildcards
When I search "Vehicle.*" using a path filter "*"
Then I should receive an error response