noe
noe copied to clipboard
chore(deps): bump sigs.k8s.io/e2e-framework from 0.2.0 to 0.3.0
Bumps sigs.k8s.io/e2e-framework from 0.2.0 to 0.3.0.
Release notes
Sourced from sigs.k8s.io/e2e-framework's releases.
v0.3.0
This is the third release of the 2023 after nearly four months of active contribution from the community. This release packs a great deal of interesting features, fixes, and documentation updates. Let's highlight some of them below.
Thread Safe Test Context
When Parallel test features where enabled and integrated into the framework, it was enabled with room for running into race conditions. In this release we have included changes that helps us mitigate these issues when the tests are being run in parallel. This has been achieved by doing the following mechanism.
- Populate the test context via the
BeforeEachTesthandler- Generate a child context from the parent context and provide that for individual tests/assessments
- Discard the context from step 2 after the tests are done
- Pass the original parent context to the
AfterEachTesthandlerAs part of the said changes to mitigate the race condition, we also extended the
Environment.TestandEnvironment.TestInParallelfunction to return acontext.Contextback after the execution of the tests have been completed. This also allows for better debugging of test context to analyze failures better with the added advantage that this is not breaking any of the existing contracts. However, if you are using agolintinfra and haveerrchecklinter enabled, you will have to make a few changes to your code to account for the newly returned value from theEnvironment.TestandEnvironment.TestInParallelfunctions.Limitations
- The Finish phase will only be able to see the context from the Setup phase and not the one from the features themselves.
Related Issues
Related Pull Requests
Continubutors
FluxCD Integration
e2e-frameworkhas had helm workflow integrated under the third_party support package for a while and now, we are addingFluxCDto that arsenal. With this integration, now you can integrate your e2e tests to run against a repository using fluxcd constructs. The supported features include the following.
- Install FluxCD components onto your cluster
- Create and Delete
GitRepositoryresource- Create and Delete
KustomizationresourceRelated Pull Requests
Contributors
kwokIntegration as a Cluster ProviderBy default,
e2e-frameworkhas two ways to run tests. One could bring up a new cluster usingkindand run thee2etests against them using the framework or integrate against a real cluster and run tests against them. In this release,kwokis being added to that list of supported cluster providers.
... (truncated)
Commits
2ac6076Merge pull request #306 from kubernetes-sigs/dependabot/github_actions/gorele...a47896fBump goreleaser/goreleaser-action from 4.3.0 to 4.4.0f02afbaMerge pull request #305 from kubernetes-sigs/dependabot/github_actions/action...fdad64bBump actions/setup-go from 4.0.1 to 4.1.024332ebMerge pull request #304 from kubernetes-sigs/dependabot/go_modules/sigs.k8s.i...f1c6ac8Bump sigs.k8s.io/controller-runtime from 0.15.0 to 0.15.11af0fd6Merge pull request #255 from matrus2/fluxc5714bbMerge pull request #298 from harshanarayana/feature/enable-issue-tempaltesba50b27Merge pull request #246 from harshanarayana/cluster-provider-interface-defini...5fa0a64Merge pull request #292 from phisco/fix/tParallel-passing-almost-everywhere- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
@dependabot rebase
Superseded by #121.