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

Charts testing #148

Closed
wolf4ood opened this issue Mar 27, 2023 · 3 comments
Closed

Charts testing #148

wolf4ood opened this issue Mar 27, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@wolf4ood
Copy link
Contributor

Helm supports testing out of the box for the Charts.
It would cool to introduce such testing in our CI pipeline.

We could probably use our Observability API for checking that the chart works as expected.

The docs for the Helm testing framework it's available here

@wolf4ood wolf4ood added the enhancement New feature or request label Mar 27, 2023
@tuncaytunc-zf
Copy link
Contributor

tuncaytunc-zf commented Mar 27, 2023

Do we really need this by now? In our current business-tests we are using the helm charts to deploy two connectors, it would fail if something is wrong with them. At least this how the business-tests are implemented by now, this might be changed if we want to refactor it.

@wolf4ood
Copy link
Contributor Author

If I got it now business runs only with the configuration postgfres and hashicorp vault. So for example we are not testing the azure variant right?

We could have a fine grained test case on each charts variant/configuration without the need to run business tests against all of them.

@tuncaytunc-zf
Copy link
Contributor

If I got it now business runs only with the configuration postgfres and hashicorp vault. So for example we are not testing the azure variant right?

We could have a fine grained test case on each charts variant/configuration without the need to run business tests against all of them.

We only have one helm chart tractusx-connector and using always the same helm chart to deploy the different variants. We just provide different image name and of course same other variables depending on the variant. Testing the azure variant would mean only provide the certain image name for azure and the required variables for it.
If we split the current business-tests into different tests then probably we would need a separate test only for helm chart but as of now I don't think this is required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

3 participants