Skipping the Gateway API tests when Gateway API is not enabled using Cypress hooks #6105
Conversation
This file contains 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
matejnesuta
added
the
test: front-end/cypress
ScriptingShrimp
requested changes
May 4, 2023
matejnesuta
force-pushed
the
gateway-setup-addition
branch
from
82c7044
to
d4a3e96
Compare
jshaughn
approved these changes
May 9, 2023
|
@ScriptingShrimp Do you approve, shall we merge this one? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There has already been some usage of the tags in the gherkin code. However, you can also use Cypress hooks with these to allow for some specific setups or teardowns when needed. This PR is meant to be a PoC of this Cypress feature.
To demonstrate this:
@gateway-apitagto be skipped/pendingpassing instead of running and failing due to the Gateway API not being enabledThis approach might be useful in the future for the multicluster testing or the parallel execution of the Cypress suite. I am also planning to resolve the #6073 issue in a similiar fashion.
Props to @ScriptingShrimp for guiding me through this.