-
Notifications
You must be signed in to change notification settings - Fork 62
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
PR to fix the issues reported by the Issue 28 #45
Conversation
cmoulliard
commented
Oct 18, 2023
- PR to fix the issues reported by the Issue Fix tests #28
…rce file under localbuild/resources/argo and file contains 55 and not 57 objects Signed-off-by: cmoulliard <[email protected]>
…ig within the cluster_test.go Signed-off-by: cmoulliard <[email protected]>
kind cluster config comparison is failing part of the cluster_test.go test as additional chars are included such as: Fixed with commit: 8034b46 |
…ith Testify Assert which simplifies comparisons and improve testing readibility Signed-off-by: cmoulliard <[email protected]>
… is mandatory for the integration tests to launch first docker Signed-off-by: cmoulliard <[email protected]>
…have to install manually a registry on docker for the test: image_test.go Signed-off-by: cmoulliard <[email protected]>
…loyment resource will be available Signed-off-by: cmoulliard <[email protected]>
Is a docker registry created OOTB when we execute |
Yeah docker is one of tools that's included in the Ubuntu image that GitHub provides. I think I want to hold off on moving to test containers, if we use Gitea like you suggested, we don't need to build images. |
I agree with you. Nevertheless, if it is need to bump a container during some tests execution, using TestContainer will simplify our life |
As most of the issues have been fixed, I propose to close this PR. WDYT ? @nabuskey |
Yeah let's close this and thanks for working on this. I do like your approach with TestContainers though. If a need arises for something like this, we should definitely consider it. |