Repository navigation
Quiet the web test output - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Requested by Frederik · project thread
Before:
npm testinweb/printed every sign-in email and the spam-filter outage warnings between the test results.After: the test output is just the results. When a test fails, the console output it produced is printed under it, so the error log and the mails are there when they help.
How:
app.test.tsswapsconsole.log/error/warnfor a collector inbeforeEachand restores them inafterEach, which dumps the collected lines if the test did not pass. The spam-filter test reads its admin alerts from the same collector instead of patchingconsole.logitself. The app is unchanged, soMAILER=logstill prints mails innpm run dev.