tests: use supertest to check response header values #2992
Closed
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.
This is an alternative pull request for #2983 converting the usages to use
supertest
rather than continuing to usesupertest
. This helps align with goals like removing theshould
module from tests eventually, since there are no lessshould
usages (plus,supertest
provides these features).The cause for these two pull requests is that there is discussion going on currently to change the prototype of the
headers
object fromObject
tonull
, which would remove global extension properties like.should
.