QA-15374: Fix test as non-renderable pages now have a warning popup #26
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
baptistegrimaud
changed the title
jkevan
approved these changes
Jan 13, 2025
baptistegrimaud
deleted the
QA-15374-error-handling-when-page-not-renderable
branch
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.
https://jira.jahia.org/browse/QA-15374
Description
Since Jahia/jcontent#1382, a dialog is now displayed if a page can't be rendered (by checking if a GraphQL query to check renderable content returns any errors), which is breaking
crashingViewTest.cy.ts, that is checking the error information is correctly displayed.A test has been added (see here) so a test in this repository is no longer needed.