Skip to content
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

Improve Jest's console output flow #1349

Closed
d4vidi opened this issue May 1, 2019 · 0 comments · Fixed by #1351
Closed

Improve Jest's console output flow #1349

d4vidi opened this issue May 1, 2019 · 0 comments · Fixed by #1351

Comments

@d4vidi
Copy link
Collaborator

d4vidi commented May 1, 2019

Is your feature request related to a problem? Please describe.
When using Jest as the test runner, console output is hard to make sense of due to these two main issues:

  1. Jest suite-level summary logs take precedence over 'plain' output, which makes them and all other logs (e.g. user in-test logging) seem cluttered.
  2. Plain logs output is batched, and thus often does not show in real-time as the test is run. This is particularly annoying when running tests on the local computer.
  3. Jest does not offer spec-level logging => no way to tell what's running "right now" and which test created what log-outputs.

Describe the solution you'd like
Allow for a configuration scheme that would streamline all logs (user and jest's), and would output them in real time.

Describe alternatives you've considered
N/A

Additional context
N/A

@d4vidi d4vidi self-assigned this May 1, 2019
@d4vidi d4vidi changed the title Improve Jest's output Improve Jest's console output flow May 1, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant