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
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:
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.
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.
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
The text was updated successfully, but these errors were encountered:
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:
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
The text was updated successfully, but these errors were encountered: