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
{{ message }}
Repository navigation
apps:run test with lengthy output -- don't log actual output on failure #360
When/if this apps:run test fails, the Expect statement proceeds to log the entire command's output, corrupting the user's terminal and crowding out logs with byte code.
We should re-jigger the test, perhaps checking first if the byte array does not match expected (outside of Expect) and then, if not, logging some standard error/failure message accordingly.
Alas, since the output is stored in sess.Out.ContentsI(), Ginkgo will log this anytime the test fails (no matter how test is failed). Wondering if there's another way to eliminate logging of output? Or, another way to test this case? ping @mboersma
Activity
vdice commentedon May 31, 2017
Alas, since the output is stored in
sess.Out.ContentsI(), Ginkgo will log this anytime the test fails (no matter how test is failed). Wondering if there's another way to eliminate logging of output? Or, another way to test this case? ping @mboersmaCryptophobia commentedon Mar 21, 2018
This issue was moved to teamhephy/workflow-e2e#2