ReporterDispatcher set result.console to undefined

[jkblume]

🐛 Bug Report

The ReporterDispatcher overrides TestResult.console property with undefined. As a result of this - the console output cannot be used in custom reporters like jest-junit.

To Reproduce

This behaviour is visible in the source code in version @jest core 24.8.0.

Line 43:
https://github.com/facebook/jest/blob/master/packages/jest-core/src/ReporterDispatcher.ts

    // Release memory if unused later.
    testResult.sourceMaps = undefined;
    testResult.coverage = undefined;
    testResult.console = undefined;

Expected behavior

The console output should be forwarded to the test reporters. But first we have to check for what reason the console property is set to undefined.

Link to repl or repo (highly encouraged)

Steps to reproduce the 'error':

• Clone the project https://github.com/jkblume/simple-app and step into it
• npm install
• npm run test

If you debug the code or add some debug outputs you notice that the TestResult.console property is defined - but after passing the ReporterDispatcher it is set to undefined

[brownbl1]

I'm seeing this as well.

[palmerj3]

I think I have a fix for jest to re-enable this functionality. Sending a PR shortly.

[SimenB]

I missed this issue, sorry! Background is in #8233. Essentially - if you need the console output at the end of a run, buffer it yourself on a test by test basis.

There's most probably some faulty types here that could have made that error visible, at least to TS users.

[hmschreiner]

Any updates on this, @SimenB?

I'm trying to create a custom reporter to sets a max warning threshold like --max-warnings on lint, but I can't figure out if the console is being called if the return of result.console is undefined.

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.