Open
Conversation
Kirdock
force-pushed
the
test/e2e-setup
branch
from
1bc2dc2 to
1148111
Compare
Kirdock
force-pushed
the
test/e2e-setup
branch
from
1148111 to
268f20b
Compare
This adds a setup step to the pipeline before the integration tests are executed, ensuring that long-running resources are created before the tests run.
Kirdock
force-pushed
the
test/e2e-setup
branch
from
268f20b to
2036fbb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a setup step to the pipeline before the integration tests are executed, ensuring that long-running resources are created before the tests run.
Why this PR?
Some E2E tests (e.g., examples) refer to existing objects (e.g., management zones, request attributes, process groups, etc.). As this can easily break if someone just deletes something in the environment, we need to remove hardcoded IDs and create the needed dependencies on demand.
Because some resources take a long time to create, it's not feasible to create them in each example/test.
Therefore ,we need a setup that creates them once, before the actual tests run.
What has changed?
Required resources are created before the integration tests start.
How does it do it?
By using our the latest published provider to create the needed resources on demand.
If they don't exist, they will be created and if they exist, the step will be ignored.
The current implementation doesn't need a state file. It's either "import" or "create".
How is it tested?
Manual tests and verified the pipeline
How does it affect users?
N/A
Issue: CA-18113