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
I am proposing that we introduce a custom consoleReporter which fixes both of these "shortcomings".
I have a prototype that makes the output look like this:
This makes the output more terse, but not necessarily easier to read. It is only easier to read, if the test names are too long, like in #4591, which can be generally worked around (by using shorter test names).
Additionally, I would propose a succinct summary at the end of the test execution if the test failed, which should fix my first issue with the consoleReporter.
If we had a custom consoleReporter, this would be relatively easy to add.
The text was updated successfully, but these errors were encountered:
There are two issues with the current
consoleReporter
(which are both mostly nitpicks and my personal preference).I am proposing that we introduce a custom
consoleReporter
which fixes both of these "shortcomings".I have a prototype that makes the output look like this:
This makes the output more terse, but not necessarily easier to read. It is only easier to read, if the test names are too long, like in #4591, which can be generally worked around (by using shorter test names).
Additionally, I would propose a succinct summary at the end of the test execution if the test failed, which should fix my first issue with the
consoleReporter
.If we had a custom
consoleReporter
, this would be relatively easy to add.The text was updated successfully, but these errors were encountered: