-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default reporter #18
Comments
Agree on this one, but should be implemented after #27 I guess. If people want the full blown output, they can then enable another reporter. |
Yeah, reporters are an important feature to implement. But I think we're not "there" yet, there are some issues that have a much higher priority. But once those are resolved, I am 100% on board with implementing custom reporters. |
@sindresorhus do you still want to work on this? I'd like to assign this to myself :) |
Go ahead ;) |
Just some quick feedback from an early user that it would be awesome to have custom reporters :) |
@alubbe That will come when we add TAP support #27. You can then use any TAP-reporter. |
Awesome, I just hope that the concurrency doesn't end up posing a problem for TAP. |
We likely will have to buffer and output one whole test at a time. |
@vdemedes ❤️ Exactly what I was thinking. |
👍 |
2 similar comments
👍 |
👍 |
I think the default reporter should be super minimal one. It should only log out detailed test info if a test fails, otherwise just
1 test passed
.It could have a live counter, so while tests are running the line is dynamically updated with
3/12 tests passed
, and when done rewritten to be12 tests passed
. That way it can be live, but also minimal.Can use log-update.
The text was updated successfully, but these errors were encountered: