Skip to content

adds selfTracing property and tests#13

Merged
codefromthecrypt merged 5 commits intomasterfrom
self-tracing-tests
Feb 19, 2024
Merged

adds selfTracing property and tests#13
codefromthecrypt merged 5 commits intomasterfrom
self-tracing-tests

Conversation

@codefromthecrypt
Copy link
Copy Markdown
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 <[email protected]>
Signed-off-by: Adrian Cole <[email protected]>
@codefromthecrypt
Copy link
Copy Markdown
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
Copy Markdown
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.

Comment thread charts/zipkin/templates/tests/test-connection.yaml Outdated
@codefromthecrypt
Copy link
Copy Markdown
Member Author

merging to make it easier to backfill ES tests

@codefromthecrypt codefromthecrypt merged commit 88717ad into master Feb 19, 2024
@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.

1 participant