forked from Comcast/plax
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathbindings-conflict.yaml
35 lines (33 loc) · 1.09 KB
/
bindings-conflict.yaml
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
doc: |
Demonstration of how one recv makes bindings that can conflict with
a subsequent recv. Also see bindings-clear.yaml,
bindings-deconflict.yaml, and bindings-star.yaml.
Note that this test is a negative test. (It's expected to fail.)
labels:
- selftest
negative: true
spec:
phases:
phase1:
steps:
- '$include<include/mock.yaml>'
- pub:
payload: '{"want":"queso"}'
- recv:
doc: |
We'll bind the pattern variable '?x'.
pattern: '{"want":"?x"}'
- pub:
payload: '{"want":"chips"}'
- recv:
doc: |
The pattern variable '?x' was bound previously to
'queso', so the following pattern is really
'{"want":"queso"}', which will not match
'{"want":"chips"}'. As a result, this step will time
out.
This test is 'negative' (see above in this
specification), so Plax will report that this test
actually succeeded.
pattern: '{"want":"?x"}'
timeout: 1s