-
Notifications
You must be signed in to change notification settings - Fork 704
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[e2e] Abstract usage of ginkgo with a new test context #3254
Conversation
9f301eb
to
99294e5
Compare
func NewTestContext() *GinkgoTestContext { | ||
return &GinkgoTestContext{} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not embed ginkgo.GinkgoT()
and possibly require.New(t)
here to cut out some of the wrapper code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean by embed? The TestContext interface does embed require.TestingT. Or are you thinking the context type should have a method to return a require instance?
Rebased |
Why this should be merged
Reuse of e2e tests and tooling requires removing direct dependency on ginkgo. This PR adds a new TestContext type that must be explicitly used to access the global ginkgo functions. This enables reuse of tmpnet glue code for #3215 (adds tmpnet support for antithesis workloads).
Next steps will include ensuring a consistent interface for test invocation to allow reuse of e2e tests in non-ginkgo environments.
How this works
How this was tested
CI