Known reporter issues

[novemberborn]

This is a list of known problems and desired improvements with our default reporter. Some may be easier to solve than others, but probably we should clean up our reporter implementation first.

• If an exception occurs when loading the test file, before it manages to declare any tests, we should say so. Originally reported in Surface errors in loading the test file, rather than misleadingly stating there are no tests #2290.

• When --match is used, if no matching tests were selected, the reporter shouldn't still print other errors that might have occurred. Originally reported in Reporters shouldn't assume the only error when --match is used is that it didn't match any tests #2191.

• Code excerpts are derived from error stack traces, but we should show the excerpt for the test itself, not wherever the error originated from. Originally reported in Ensure code excerpt is from test file, even if assertion failure occurs elsewhere #1743, might have already been resolved.

• We should print how many snapshots were updated. Originally reported in Print output when snapshots are updated #1583.

• Bad usage of the test interface is thrown as an internal error, which looks horrible. Originally reported in Report bad test() usage as a test failure, rather than a runtime error #698.

• When --match is used, or after a test.only() has been encountered, AVA still needs to launch each test file to see if there are matches or exclusive tests. There is no output while this is happening. There should be. Originally reported in Provide feedback in reporter when files are launched, but contain no matching tests #2246.

• We should revisit the color scheme. Originally reported in Feedback from color blind users #413.

• It's hard to distinguish console output between watch runs. Originally reported in Horizontal rule between successful runs with logs #1917.

• We print pending tests when AVA times out. We should print just those tests (and hooks) that have started. Originally reported in When global timeouts occur, show unfinished tests, not pending ones #2421.

• t.log() output for passing tests is only available in verbose mode. We should always print this. Originally reported in Mini reporter not printing t.log() content when test is successful #2201.

• The - & + diff symbols need an explanation. Originally reported in Explain diff gutter symbols #1558.

• Even when not in verbose mode, we should print details for all exceptions. Originally reported in Internal errors should always be verbose #2171.

• When not in verbose mode, console output from the test files messes with the reporter output. Originally reported in Mini reporter clobbers stdout #1953.

[futpib]

(Sorry for off-topic) Bounties from #1743, #1917, #1558 and #1953 are now dangling and should probably be moved here somehow.

[novemberborn]

@futpib yes, I'm not sure to what extend that's possible. @sindresorhus?

[sindresorhus]

I have copy-pasted the relevant bounty badges inline in the issue here. The combined bounty is $220.