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
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.
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)The text was updated successfully, but these errors were encountered: