You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the output of npm run mocha is littered with random log messages printed by some of the tests. This makes troubleshooting more difficult when one of the tests actually fail (e.g. on our CI), because it's not clear which messages are relevant to the test failure and which are just garbage.
We should fix all our tests so that they don't log anything on success.
Nice to have: an automated checker/linter that will fail the build when a test passes but still prints something to the console.
Acceptance criteria
The output of npm run mocha contains only a list of dot characters printed by Mocha's dot reporter.
A blog post explaining why it's a bad practice to have tests cluttering console output and what interesting design approaches and hacks we used to get rid of those logs.
The text was updated successfully, but these errors were encountered:
Right now, the output of
npm run mocha
is littered with random log messages printed by some of the tests. This makes troubleshooting more difficult when one of the tests actually fail (e.g. on our CI), because it's not clear which messages are relevant to the test failure and which are just garbage.We should fix all our tests so that they don't log anything on success.
Nice to have: an automated checker/linter that will fail the build when a test passes but still prints something to the console.
Acceptance criteria
npm run mocha
contains only a list of dot characters printed by Mocha'sdot
reporter.The text was updated successfully, but these errors were encountered: