Skip to content

apps:run test with lengthy output -- don't log actual output on failure #2

Open

Description

@Cryptophobia

From @vdice on May 26, 2017 22:17

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.

Copied from original issue: deis/workflow-e2e#360

Activity

  1. Cryptophobia commented on Mar 21, 2018

    @Cryptophobia
    MemberAuthor

    From @vdice on May 31, 2017 0:3

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions