subscribe-test: extract subscribeWithBadFn
function
#3630
Merged
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.
Two test groups use essentially the same logic to set up a subscription with an improper subscribeFn, testing both
subscribe
andcreateSourceEventStream
.This PR extracts the duplicated logic into a single common
subscribeWithBadFn
function.For convenience, the common function is typed to appropriately return a
Promise<ExecutionResult>
rather than aPromise<ExecutionResult | AsyncGenerator<...>>
). Because thesubscribeFn
is expected to be "bad," anAsyncGenerator
should never be returned. If a validsubscribeFn
is mistakenly passed, an assertion failure is triggered.extracted from #3620