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

Junit report should have system-out #1387

Open
shantanjk opened this issue Apr 13, 2024 · 1 comment
Open

Junit report should have system-out #1387

shantanjk opened this issue Apr 13, 2024 · 1 comment

Comments

@shantanjk
Copy link

shantanjk commented Apr 13, 2024

JUNIT report contains system-err only, Need support to have system-out for every it block

Exit [SynchronizedBeforeSuite] TOP-LEVEL - /code/jks/ommp_suite_test.go:159 @ 04/13/24 23:03:01.198 (39.252s)
@onsi
Copy link
Owner

onsi commented Apr 15, 2024

hey there - Ginkgo piggy backs on top of Junit's fields to provide richer information. system-err includes a full timeline of the spec including any information written to the GinkgoWriter. system-out includes any stdout/stderr captured (only available if running in parallel). what information, exactly, are you hoping to see?

In general it is an anti-pattern to emit to stdout/stderr directly in your test/code. It's better to inject an io.Writer and pass in GinkgoWriter under test so that code and test output is correctly interleaved and captured by Ginkgo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants