Remove unnecessary console output when running test cases #5384
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.
Summary
Running the tests did, for some test cases, show yarn command output like
[1/4] Resolving packages...
. This pull request captures the command output instead of printing it to the console, the same way as this is done in many other test cases.Unnecessary command output during testing makes the tests noisy. We are mostly only interested in test success or failure messages, not all the details of all the commands that run internally. Even if the command output were interesting, it usually should be captured and tested in the test, not written to console.
Test plan
The tests still pass, just with less random console output.