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

Write tests for helm chart #68

Open
batpad opened this issue Jun 18, 2018 · 1 comment
Open

Write tests for helm chart #68

batpad opened this issue Jun 18, 2018 · 1 comment
Labels
kube Related to Kubernetes configuration

Comments

@batpad
Copy link
Member

batpad commented Jun 18, 2018

https://github.com/kubernetes/helm/blob/master/docs/chart_tests.md - this seems like a great way to test - it maybe a bit more complicated for us due to the time taken for the web container to come up. But we should try and write some basic tests to get started. Getting these tests to work on Circle might be another challenge, but let that not stop us from having basic tests that can be run to verify a release works as expected.

cc @Rub21

@batpad batpad added the kube Related to Kubernetes configuration label Jun 18, 2018
@batpad batpad added this to the Release 0.2.0 milestone Jun 25, 2018
@batpad
Copy link
Member Author

batpad commented Jan 12, 2022

Bump, cc @geohacker - this would be really really nice to do.

It does seem like #25 makes this a bit tricky, but there are well established practices now to run tests for helm / k8s deploys in CI, generally using k3s to run a lightweight kubernetes cluster, install the helm chart onto it, and have some tests to check that services are working basically as expected.

This will be a bunch of work, but will be great to make a start toward, to at least have basic assurance that our basic use-cases all continue to work, especially when updating upstream code, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kube Related to Kubernetes configuration
Projects
None yet
Development

No branches or pull requests

2 participants