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
Either provide logs of test-case in TestCaseResult or make the information about the test-case where the log was created available in the LogEntry of TestResult.
Motivation
Currently the console buffer is sent to a reporter with the TestResult. This information is not very useful in cases where you want to group the logs per test-case.
It also does not seem trivial to map logs back to test-cases since the LogEntry only contains a complete stacktrace on where the log was sent from and no information during which test-case it was sent.
Because of this it's impossible without some hacks to identify the logs per test-case and report them to some external tool like reportportal/agent-js-jest#55.
Example
No response
Pitch
This enables reporters to give better context to test-execution reports.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
🚀 Feature Proposal
Either provide logs of test-case in TestCaseResult or make the information about the test-case where the log was created available in the LogEntry of TestResult.
Motivation
Currently the console buffer is sent to a reporter with the TestResult. This information is not very useful in cases where you want to group the logs per test-case.
It also does not seem trivial to map logs back to test-cases since the LogEntry only contains a complete stacktrace on where the log was sent from and no information during which test-case it was sent.
Because of this it's impossible without some hacks to identify the logs per test-case and report them to some external tool like reportportal/agent-js-jest#55.
Example
No response
Pitch
This enables reporters to give better context to test-execution reports.
The text was updated successfully, but these errors were encountered: