MNT Ensure graphql 3 versions of behat tests run #1214
Merged
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
1 task
emteknetnz
force-pushed
the
pull/1.8/behat-graphql
branch
from
f0165c5 to
be2e92e
Compare
maxime-rainville
requested changes
May 19, 2021
emteknetnz
force-pushed
the
pull/1.8/behat-graphql
branch
from
be2e92e to
8eec90d
Compare
maxime-rainville
approved these changes
May 20, 2021
|
@maxime-rainville yup graphql4 is existing failure #1215 |
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.
Issue #1213
Admin is a bit of strange one that runs both 'admin' and 'cms' behat suites. It's debatable whether things should be this way, though for now I think we should keep it as is.
This PR will ensure that both behat suites have both graphql 3 and graphql 4 jobs run
The new graphql 3 behat tests are passing, though the graphql 4 build has an existing failure