-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdormant_sessions.feature
69 lines (62 loc) · 2.88 KB
/
dormant_sessions.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
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
Feature: Dormant session
@dormant
Scenario Outline: Dormant session succeeds for a requester which does unicast requests
Given an access profile using <channel_class> which does not scan
And an access profile using <channel_class> which does scan continuously
And a requester, which does not scan
And a responder, which scans continuously
And a dormant session registered at the responder for the UID of the requester
When the requester starts a unicast session to the responder
Then the requester's session should complete successfully
And the responder should receive an unsolicited response
And the requester should receive the dormant session
And the responders's dormant session should complete successfully
Examples: example1
| channel_class |
| lo |
# | normal |
# | hi |
@dormant
Scenario Outline: Dormant session fails for a requester which does broadcast requests
Given an access profile using <channel_class> which does not scan
And an access profile using <channel_class> which does scan continuously
And a requester, which does not scan
And a responder, which scans continuously
And a dormant session registered at the responder for the UID of the requester
When the requester starts a broadcast session to the responder
Then the requester's session should complete successfully
And the responder should receive an unsolicited response
And the requester should not receive the dormant session
# TODO And the responders's dormant session should not complete successfully
Examples: example1
| channel_class |
| lo |
# | normal |
# | hi |
@dormant
Scenario Outline: Dormant session times out as expected and fails when no response
Given an access profile using <channel_class> which does not scan
And an access profile using <channel_class> which does scan continuously
And a requester, which does not scan
And a responder, which scans continuously
And a dormant session registered at the responder for the UID of the requester
When waiting for the dormant session to time out
Then the responders's dormant session should not complete successfully
Examples: example1
| channel_class |
| lo |
# | normal |
# | hi |
@dormant
Scenario Outline: Dormant session times out as expected and succeeds on response
Given an access profile using <channel_class> which does scan continuously
And a requester, which scans continuously
And a responder, which scans continuously
And a dormant session registered at the responder for the UID of the requester
When waiting for the dormant session to time out
Then the responders's dormant session should complete successfully
Examples: example1
| channel_class |
| lo |
# | normal |
# | hi |