-
Notifications
You must be signed in to change notification settings - Fork 433
chore(tests): introduce testcontainers into integration tests as a partial replacement for chainsaw #2083
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
Conversation
7ec5da8
to
74a20b6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#2073 can be merged, so you should no longer be blocked :)
55d375e
to
1d6d6bf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there's potential for code simplification and improved consistency, but I guess it's OK to do that later as reducing dependency on chainsaw and ability to test positive conditions are more important, so I don't want to block you.
I've made a few minor suggestions though on what you might want to improve right away.
c106c41
to
07050b0
Compare
Agreed, There's a likely a lot that could be done for consistency, naming, and similar. For example the added file |
07050b0
to
8327f58
Compare
Co-authored-by: Igor Beliakov <46579601+weisdd@users.noreply.github.com>
8327f58
to
a6bf4d8
Compare
I've fixed the formatting issue, so now we should be good to merge the PR. |
In a continued effort to improve CI stability, This PR introduces an External Grafana instance to Integration tests via testcontainers.
I mentioned wanting an cluster external grafana instance when running our Chainsaw E2E tests, but realised most of the benefits from that also applied to Integration tests.
Tp that end, the forced folder deletion and newly added datasource substitution tests have been migrated into Integration tests.
As unit tests are fast to run compared to integration tests, I added support for
-short
viamake test-short
.When used, integration tests(Ginkgo) are skipped.
This allows significantly faster iteration when writing unit tests.
Refactored
GetScopedMatchingInstances
integration test with new variables and more from the suite.Once merged, this allows testing positive Conditions like
Synchronized
as evident from the new tests.Coverage of controllers has gone from
35.9%
to42.2%