map test: reports partial result after an error (series & parallel) #16
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.
These test cases cover the effects of a
for
loop ininitializeResults()
, inlib/helpers.js
.Without this kind of a test case, it would be possible to remove the
for
loop (and an internal variable) without failing the test suite:This is a code mutation that I discovered through mutation testing using Stryker Mutator, which I will propose in an upcoming PR.
For the parallel
map
API call, the test case waits for both the callback and remaining iterator to finish. A little tricky, hopefully not too fragile:)