Skip to content

Update docs to use ginkgo instead of go test #236

@mkfdoherty

Description

@mkfdoherty

The e2e tests appear to break on spurious errors of port forward when using go test ./.... The e2e tests are written using ginkgo and using ginkgo ./... seems to not exhibit this issue. I would suggest we make this clear in the docs. It would be useful to better understand why this is the case too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions