-
Notifications
You must be signed in to change notification settings - Fork 10
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
*: Delineate between unit and integration tests #399
Conversation
The slowest test when running |
9544d69
to
988d65a
Compare
988d65a
to
b2cbc26
Compare
This commit blocks the k3d package from being used unless the `integration` or `acceptance` build tags have been provided. The primary goal of which is to reduce the total iteration time for running unit tests. Additionally, this commit makes the test name assertions of the `SkipIfNot{Integration,Acceptance}` helpers run regardless of build tags to ensure consistent naming across the codebase.
b2cbc26
to
c8af6ec
Compare
I think schema should have Prometheus and Cert-Manager CRDs added as per
|
Interesting that 2 tests reported that generation ID was changed by something ...
|
Another problem with the name length
|
I'm going to go ahead and merge this rather than trying to fix all the integration issues as those tests we're just not being run previously and they don't currently block merged. |
This commit blocks the k3d package from being used unless the
integration
oracceptance
build tags have been provided. The primary goal of which is to reduce the total iteration time for running unit tests.Additionally, this commit makes the test name assertions of the
SkipIfNot{Integration,Acceptance}
helpers run regardless of build tags to ensure consistent naming across the codebase.