-
Notifications
You must be signed in to change notification settings - Fork 35
/
v2algodclient_paths.feature
224 lines (197 loc) · 10.9 KB
/
v2algodclient_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
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
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
@unit
Feature: Algod REST API v2 Paths
Background:
Given mock server recording request paths
# SendRaw, Status, Supply, SuggestedParams, and PendingTransactionsInformation omitted - the path never mutates, they're constant
@unit.algod
Scenario Outline: Pending Transaction Information
When we make a Pending Transaction Information against txid "<txid>" with format "<format>"
Then expect the path used to be "<path>"
Examples:
| path | txid | format |
| /v2/transactions/pending/5FJDJD5LMZC3EHUYYJNH5I23U4X6H2KXABNDGPIL557ZMJ33GZHQ?format=msgpack | 5FJDJD5LMZC3EHUYYJNH5I23U4X6H2KXABNDGPIL557ZMJ33GZHQ | msgpack |
@unit.algod
Scenario Outline: Pending Transaction Information2
When we make a Pending Transaction Information with max <max> and format "<format>"
Then expect the path used to be "<path>"
Examples:
| path | max | format |
| /v2/transactions/pending?format=msgpack | 0 | msgpack |
| /v2/transactions/pending?format=msgpack&max=1 | 1 | msgpack |
@unit.algod
Scenario Outline: Pending Transactions By Address
When we make a Pending Transactions By Address call against account "<account>" and max <max> and format "<format>"
Then expect the path used to be "<path>"
Examples:
| path | account | max | format |
| /v2/accounts/7ZUECA7HFLZTXENRV24SHLU4AVPUTMTTDUFUBNBD64C73F3UHRTHAIOF6Q/transactions/pending?format=msgpack | 7ZUECA7HFLZTXENRV24SHLU4AVPUTMTTDUFUBNBD64C73F3UHRTHAIOF6Q | 0 | msgpack |
| /v2/accounts/7ZUECA7HFLZTXENRV24SHLU4AVPUTMTTDUFUBNBD64C73F3UHRTHAIOF6Q/transactions/pending?format=msgpack&max=1 | 7ZUECA7HFLZTXENRV24SHLU4AVPUTMTTDUFUBNBD64C73F3UHRTHAIOF6Q | 1 | msgpack |
@unit.algod
Scenario Outline: Status After Block
When we make a Status after Block call with round <round>
Then expect the path used to be "<path>"
Examples:
| path | round |
| /v2/status/wait-for-block-after/0 | 0 |
@unit.algod
Scenario Outline: Account Information
When we make an Account Information call against account "<account>"
Then expect the path used to be "<path>"
Examples:
| path | account |
| /v2/accounts/7ZUECA7HFLZTXENRV24SHLU4AVPUTMTTDUFUBNBD64C73F3UHRTHAIOF6Q | 7ZUECA7HFLZTXENRV24SHLU4AVPUTMTTDUFUBNBD64C73F3UHRTHAIOF6Q |
@unit.algod
Scenario Outline: Get Block
When we make a Get Block call against block number <round> with format "<format>"
Then expect the path used to be "<path>"
Examples:
| path | round | format |
| /v2/blocks/0?format=msgpack | 0 | msgpack |
@unit.applications
Scenario Outline: GetAssetByID
When we make a GetAssetByID call for assetID <asset-id>
Then expect the path used to be "<path>"
Examples:
| path | asset-id |
| /v2/assets/1234 | 1234 |
@unit.applications
Scenario Outline: GetApplicationByID
When we make a GetApplicationByID call for applicationID <application-id>
Then expect the path used to be "<path>"
Examples:
| path | application-id |
| /v2/applications/1234 | 1234 |
@unit.applications.boxes
Scenario Outline: GetApplicationBoxByName
When we make a GetApplicationBoxByName call for applicationID <application-id> with encoded box name "<encoded-box-name>"
Then expect the path used to be "<path>"
Examples:
| path | application-id | encoded-box-name |
| /v2/applications/1234/box?name=b64%3AaGVsbG8%3D | 1234 | b64:aGVsbG8= |
| /v2/applications/1234/box?name=b64%3A%2Fw%3D%3D | 1234 | b64:/w== |
| /v2/applications/1234/box?name=b64%3A8J%2BSqQ%3D%3D | 1234 | b64:8J+SqQ== |
| /v2/applications/1234/box?name=b64%3AYS96 | 1234 | b64:YS96 |
@unit.applications.boxes
Scenario Outline: GetApplicationBoxes
When we make a GetApplicationBoxes call for applicationID <application-id> with max <max>
Then expect the path used to be "<path>"
Examples:
| path | application-id | max |
| /v2/applications/1234/boxes | 1234 | 0 |
| /v2/applications/1234/boxes?max=2 | 1234 | 2 |
@unit.algod.ledger_refactoring
Scenario Outline: Account Information
When we make an Account Information call against account "<account>" with exclude "<exclude>"
Then expect the path used to be "<path>"
Examples:
| path | account | exclude |
| /v2/accounts/47YPQTIGQEO7T4Y4RWDYWEKV6RTR2UNBQXBABEEGM72ESWDQNCQ52OPASU | 47YPQTIGQEO7T4Y4RWDYWEKV6RTR2UNBQXBABEEGM72ESWDQNCQ52OPASU | |
| /v2/accounts/47YPQTIGQEO7T4Y4RWDYWEKV6RTR2UNBQXBABEEGM72ESWDQNCQ52OPASU?exclude=all | 47YPQTIGQEO7T4Y4RWDYWEKV6RTR2UNBQXBABEEGM72ESWDQNCQ52OPASU | all |
@unit.algod.ledger_refactoring
Scenario Outline: Account Asset Information
When we make an Account Asset Information call against account "<account>" assetID <asset-id>
Then expect the path used to be "<path>"
Examples:
| path | account | asset-id |
| /v2/accounts/47YPQTIGQEO7T4Y4RWDYWEKV6RTR2UNBQXBABEEGM72ESWDQNCQ52OPASU/assets/123 | 47YPQTIGQEO7T4Y4RWDYWEKV6RTR2UNBQXBABEEGM72ESWDQNCQ52OPASU | 123 |
@unit.algod.ledger_refactoring
Scenario Outline: Account Application Information
When we make an Account Application Information call against account "<account>" applicationID <application-id>
Then expect the path used to be "<path>"
Examples:
| path | account | application-id |
| /v2/accounts/47YPQTIGQEO7T4Y4RWDYWEKV6RTR2UNBQXBABEEGM72ESWDQNCQ52OPASU/applications/123 | 47YPQTIGQEO7T4Y4RWDYWEKV6RTR2UNBQXBABEEGM72ESWDQNCQ52OPASU | 123 |
@unit.paths.stateproof
Scenario Outline: GetTransactionProof
When we make a GetTransactionProof call for round <round> txid "<txid>" and hashtype "<hashtype>"
Then expect the path used to be "<path>"
Examples:
| path | round | txid | hashtype |
| /v2/blocks/123/transactions/5FJDJD5LMZC3EHUYYJNH5I23U4X6H2KXABNDGPIL557ZMJ33GZHQ/proof?format=msgpack | 123 | 5FJDJD5LMZC3EHUYYJNH5I23U4X6H2KXABNDGPIL557ZMJ33GZHQ | |
| /v2/blocks/123/transactions/5FJDJD5LMZC3EHUYYJNH5I23U4X6H2KXABNDGPIL557ZMJ33GZHQ/proof?format=msgpack&hashtype=sha512_256 | 123 | 5FJDJD5LMZC3EHUYYJNH5I23U4X6H2KXABNDGPIL557ZMJ33GZHQ | sha512_256 |
@unit.stateproof.paths
Scenario Outline: GetLightBlockHeaderProof
When we make a GetLightBlockHeaderProof call for round <round>
Then expect the path used to be "<path>"
Examples:
| path | round |
| /v2/blocks/123/lightheader/proof | 123 |
@unit.stateproof.paths
Scenario Outline: GetStateProof
When we make a GetStateProof call for round <round>
Then expect the path used to be "<path>"
Examples:
| path | round |
| /v2/stateproofs/123 | 123 |
@unit.blocksummary
Scenario Outline: LookupBlockHash path
When we make a Lookup Block Hash call against round <round>
Then expect the path used to be "<path>"
Examples:
| path | round |
| /v2/blocks/3/hash | 3 |
@unit.statedelta
Scenario Outline: GetLedgerStateDelta path
When we make a GetLedgerStateDelta call against round <round>
Then expect the request to be "<method>" "<path>"
Examples:
| path | method | round |
| /v2/deltas/3?format=msgpack | get | 3 |
@unit.sync
Scenario Outline: SetSyncRound path
When we make a SetSyncRound call against round <round>
Then expect the request to be "<method>" "<path>"
Examples:
| path | method | round |
| /v2/ledger/sync/3 | post | 3 |
@unit.sync
Scenario Outline: GetSyncRound path
When we make a GetSyncRound call
Then expect the request to be "<method>" "<path>"
Examples:
| path | method |
| /v2/ledger/sync | get |
@unit.sync
Scenario Outline: UnsetSyncRound path
When we make a UnsetSyncRound call
Then expect the request to be "<method>" "<path>"
Examples:
| path | method |
| /v2/ledger/sync | delete |
@unit.timestamp
Scenario Outline: SetBlockTimeStampOffset path
When we make a SetBlockTimeStampOffset call against offset <offset>
Then expect the request to be "<method>" "<path>"
Examples:
| path | method | offset |
| /v2/devmode/blocks/offset/123 | post | 123 |
@unit.timestamp
Scenario Outline: GetBlockTimeStampOffset path
When we make a GetBlockTimeStampOffset call
Then expect the request to be "<method>" "<path>"
Examples:
| path | method |
| /v2/devmode/blocks/offset | get |
@unit.txngroupdeltas
Scenario Outline: LedgerStateDeltaForTransactionGroupResponse
When we make a LedgerStateDeltaForTransactionGroupResponse call for ID "<id>"
Then expect the path used to be "<path>"
Examples:
| path | id |
| /v2/deltas/txn/group/JQKUGWTENQUYD64IRVJTZ7226BIEBZU2WDMPPMWJSA4FXIPRMWYQ?format=msgpack | JQKUGWTENQUYD64IRVJTZ7226BIEBZU2WDMPPMWJSA4FXIPRMWYQ |
| /v2/deltas/txn/group/4MGYPT5CU5O3KRPKYTLBXL4XANTKQNL4P5ZPVFNVFUFMZNUY6E5A?format=msgpack | 4MGYPT5CU5O3KRPKYTLBXL4XANTKQNL4P5ZPVFNVFUFMZNUY6E5A |
@unit.txngroupdeltas
Scenario Outline: TransactionGroupLedgerStateDeltaForRoundResponse
When we make a TransactionGroupLedgerStateDeltaForRoundResponse call for round <round>
Then expect the path used to be "<path>"
Examples:
| path | round |
| /v2/deltas/25/txn/group?format=msgpack | 25 |
| /v2/deltas/1001/txn/group?format=msgpack | 1001 |
@unit.blocktxids
Scenario Outline: Get Block TXIDs
When we make a GetBlockTxids call against block number <round>
Then expect the path used to be "<path>"
Examples:
| path | round |
| /v2/blocks/29608182/txids | 29608182 |