-
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
Error from gingko tests: flag provided but not defined #3760
Comments
I added this to my
This seems related to #2731 but should already be fixed in v0.19.x if I read it correctly. |
HI @gee4vee, The test-framework as the command However, you are also able to use envtest with the adopted libs ( gingko/gomega ) in projects scaffold with the previous versions. But it means, call and use it as described below and not with
See that in the new layout (1.0) projects are scaffolded with the makefile target NOTE: In the above documentation you will see links which will bring more info and examples. Feel free to check the SDK tests to ensure the Helm projects scaffold with the tool and the controller-runtime tests as just examples of the tests with the stack adopted too. I hope that it helps you with. |
Flag as doc since we need to provide better guidance on how to do the tests. @dmesser also suggested we have a section to cover testing in it’s own chapter, most likely per operator-type (golang, ansible, helm) etc. |
Thanks for the guidance! We will likely migrate our project to get it working. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Bug Report
We are in the process of writing E2E tests using gingko/gomega and hit this error when trying to run them locally.
WIP code is here: IBM/starter-kit-operator#6
What did you do?
Execute
operator-sdk test local ./test/e2e --up-local --operator-namespace=e2e-testing --debug
What did you expect to see?
Tests are executed
What did you see instead? Under which circumstances?
Environment
operator-sdk version: v0.19.2
go version: go1.14.5 darwin/amd64
Kubernetes version information: v1.18.2
Kubernetes cluster kind: OpenShift 4.3
Are you writing your operator in ansible, helm, or go? go
Possible Solution
Additional context
The text was updated successfully, but these errors were encountered: