Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make buffered console output available to testResultsProcessor
See original GitHub issueDo you want to request a feature or report a bug?
feature
What is the current behavior?
A testResultsProcessor is given access to a lot of meaningful data but one thing not yet available is the console output from each test case.
What is the expected behavior?
It would be very helpful to provide the buffered console output to test results processors like jest-junit to include console output for each <testcase> (see https://github.com/palmerj3/jest-junit/issues/45 for more details).
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Interesting! I think this should be possible, but I haven’t dug into it.
That seems super silly. I’ve been looking at the console stuff lately, and we should definitely still populate
consoleeven though we suppress the output in the default reporter.