-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test,hack: add e2e test for new project layout #3060
Conversation
5782d11
to
d6c5115
Compare
15a20e4
to
a1c9fb9
Compare
884ad21
to
96e249d
Compare
dd95359
to
a7a0af9
Compare
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.
/lgtm
/approve
It shows great for me 👍
It is doing the test and we can improve it according to our needs.
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.
Pretty much LGTM except we probably want to make it explicitly clear in the script that we're not using envtest right now.
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.
LGTM after adding a comment on why we're setting up envtest vars.
a7a0af9
to
ccd6cf9
Compare
New changes are detected. LGTM label has been removed. |
ccd6cf9
to
0a02611
Compare
Description of the change:
operator-sdk init
'd)test-e2e-go-new
to run the test suiteMotivation for the change: we need a simple e2e test that ensures changes made to the underlying kubebuilder plugin result in a valid operator, without duplicating much code from upstream e2e tests.
Note: once kubernetes-sigs/kubebuilder#1520 is merged,
/test/e2e-new/util
can be removed.