Skip to content
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

Make passing Travis required for merge #13

Closed
saad-ali opened this issue Aug 13, 2018 · 6 comments
Closed

Make passing Travis required for merge #13

saad-ali opened this issue Aug 13, 2018 · 6 comments
Assignees

Comments

@saad-ali
Copy link
Member

Make passing Travis required for merge

xref kubernetes/test-infra#9014 (comment)

/assign @sbezverk

@sbezverk
Copy link
Contributor

@saad-ali to really test it that would require a k8s cluster or minikube, should I add a sort of integration test, brining k8s and then starting liveness probe?

@jsafrane
Copy link
Contributor

Travis runs go vet, make, gofmt and go test, all this is great to have (and it should succeed before merge). However, I don't see any real tests. go test does not run anything.

So yes, let's make travis mandatory, but also let's prepare real tests. Liveness probe is a simple executable that talks to CSI driver and returns error when Probe() fails. All this can be tested outside of Kubernetes easily with a mock CSI driver.

@sbezverk
Copy link
Contributor

@jsafrane I can add a small script to travis to start hostpath driver and liveness probe and check the result of a probe. Would it be sufficient for testing?

@jsafrane
Copy link
Contributor

Yes, that's a good start. And a script that runs just the probe and no driver (-> timeout or connection refused? -> nozero exit code) should be easy too and it would cover one error case.

@spiffxp
Copy link
Contributor

spiffxp commented Aug 14, 2018

@sbezverk
Copy link
Contributor

pohly pushed a commit to pohly/livenessprobe that referenced this issue Apr 11, 2019
jsafrane pushed a commit to jsafrane/livenessprobe that referenced this issue Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants