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

[Feature]: Provide console logs per testcase to reporter #15180

Closed
cgrabmann opened this issue Jul 11, 2024 · 4 comments
Closed

[Feature]: Provide console logs per testcase to reporter #15180

cgrabmann opened this issue Jul 11, 2024 · 4 comments

Comments

@cgrabmann
Copy link

🚀 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.

Copy link

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

@github-actions github-actions bot added the Stale label Aug 10, 2024
Copy link

github-actions bot commented Sep 9, 2024

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.

1 similar comment
Copy link

github-actions bot commented Sep 9, 2024

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 github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 9, 2024
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant