Ensure test after() callback is always executed #3936
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.
This PR contains:
Are tests included?
N/A - The fix is for the test suite itself.
Breaking Changes?
List any relevant issue numbers:
Description
Took me a little while to track down what was going on here. Basically, if the
emit-uint8array-no-buffer
test fails, then all subsequent tests will fail to execute. This is because theemit-uint8array-no-buffer
test has abefore
function which deletesglobal.Buffer
, and and anafter
function which is supposed to restore it.However, prior to this PR, the
after
callback is not guaranteed to be called soglobal.Buffer
remains undefined. The lack ofglobal.Buffer
causes issues with, magic-string, but likely elsewhere too.rollup/test/form/samples/emit-uint8array-no-buffer/_config.js
Lines 6 to 11 in 889fa52