From npm/cli#8621:
My only complaint about the failures is that I didn't immediately know to search for not ok. It'd be nice if failing tests said:
Search for not ok to identify failures.
This is not a trivial thing to solve, since not ok only shows up in CI and other non-tty environments. So a blanket statement like that would not make much sense. We'd either need a custom default tap reporter or we'd need some kind of test running wrapper to display that output, and then only when applicable.
Opening this ticket to record this idea at least.
From npm/cli#8621:
This is not a trivial thing to solve, since
not okonly shows up in CI and other non-tty environments. So a blanket statement like that would not make much sense. We'd either need a custom default tap reporter or we'd need some kind of test running wrapper to display that output, and then only when applicable.Opening this ticket to record this idea at least.