Closed ajewellamz closed 3 months ago
Neither. I agree that properly completed and merged tests should not print. Back in my C++ days, I had my CI enforce that.
However, during development it is SUPER useful to be able to throw in a quick eprintln!
to try to figure out what is happening.
As a side benefit, if our tests should not be printing, then this will at least allow the possibility that we notice that a test is printing.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.