test(e2e): tolerate legacy-environment content on deploy-test - #179
Merged
Conversation
The test/production sites still serve the master Contentful environment (legacy SEO Meta Data entry, MUI footer), which PR CI never exercises. Accept both content shapes; the SEO legacy arm goes away after the environment switch, the dropdown label alternation stays while csforall uses the MUI footer.
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
2 participants
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.
masterContentful environment (legacy content model) — a combination PR CI (which usesdevelopment) never exercises. Two tests failed across all browsers/brands on run 30815853217.Select language(redesigned Code.org footer) andLanguage selection dropdown(MUI footer, used by csforall permanently and by corporate on the legacy environment).arlanguage switch through the legacy dropdown.