feat: support array-type response body #3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SteveLauC
force-pushed
the
steve/feat/array_type_response_body
branch
2 times, most recently
from
25eddfa to
d7bab4f
Compare
This commit allows us to do assertions against array-type response body:
```
POST /resources/shares/_batch_get
[
{
"resource_id": "$[[env.DATASOURCE_1_DOCUMENT_FILE_A_ID]]",
}
]
# assert: (200,
# [
# {
# "permission": 8,
# "principal_id": "$[[env.A_ID]]"
# },
# {
# "permission": 4
# }
# ])
```
This was not implemented primarily because Loadgen did not support it,
which will be solved by PR [1].
[1]: infinilabs/loadgen#41
SteveLauC
force-pushed
the
steve/feat/array_type_response_body
branch
from
d7bab4f to
78289fc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: support array-type response body
This commit allows us to do assertions against array-type response body:
This was not implemented primarily because Loadgen did not support it,
which will be solved by PR 1.