Rename expect(worker:producingOutput:)
to be more clear about what it is asserting
#323
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.
When I first saw tests that used this function, I thought it was asserting that the
worker
passed in, matches theworkflow.worker
(which it does do), and that it was asserting thatproducingOutput == workflow.worker.output
(which it does NOT do). Instead, neither of the workers are ever run. TheproducingOutput
is used as mock output. So renaming these to make it more clear what is going on.Checklist