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

adds selfTracing property and tests #13

Merged
merged 5 commits into from
Feb 19, 2024
Merged

Conversation

codefromthecrypt
Copy link
Member

In looking at #11 I noticed there are no examples of actual integration tests. This uses self-tracing arbitrarily to show how to do it.

Signed-off-by: Adrian Cole <adrian@tetrate.io>
Adrian Cole added 2 commits February 19, 2024 16:31
Signed-off-by: Adrian Cole <adrian@tetrate.io>
Signed-off-by: Adrian Cole <adrian@tetrate.io>
@codefromthecrypt
Copy link
Member Author

so the key here is that ct install runs all the configuration in ci/*values.yaml

@@ -0,0 +1,23 @@
apiVersion: v1
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is different about most helm charts is even if they have a 'ci' directory, they don't have a test pod. So unless I am missing something, you only test that the thing didn't crash on ct install. This file allows you to write some things without moving to a more fancy framework like https://github.com/helm-unittest/helm-unittest (not sure that one is unit tests or integration, but anyway not using it yet)

Thanks @tamalsaha for pointing it out, in case we do use it one day.

@codefromthecrypt
Copy link
Member Author

merging to make it easier to backfill ES tests

@codefromthecrypt codefromthecrypt merged commit 88717ad into master Feb 19, 2024
1 check passed
@codefromthecrypt codefromthecrypt deleted the self-tracing-tests branch February 19, 2024 23:33
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

Successfully merging this pull request may close these issues.

None yet

1 participant