-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Remove erroneous <br> tags from error messages #28496
Conversation
Can you add a test for the affirmative case where it does keep |
@brian-mann Yah these original tests are still there: https://github.com/cypress-io/cypress/pull/25467/files#diff-95c9055c314a4b42dab5687daf7ea43804e5ec4d3d613632153b0dbde2d33e96R56 |
4 flaky tests on run #52749 ↗︎
Details:
runs.cy.ts • 2 flaky tests • app-e2especs_list_latest_runs.cy.ts • 1 flaky test • app-e2e
debug.cy.ts • 1 flaky test • app-e2e
Review all test suite changes for PR #28496 ↗︎ |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Additional details
There was a regression introduced in 12.4.0 with this PR, where all of our error messages were formatting to include
<br>
tags when there was a new line in the error message.The original PR did not run Percy checks since it was an outside contributor, so this visual change went unnoticed.
This adds an exception to the formatting logic when the message is of type: error in order to maintain the functionality of the originally intended PR to have line breaks in Cypress.log messages.
Steps to test
A test was added to cover this in the test_errors.cy.ts, we should also see Percy snapshots update.
How has the user experience changed?
Before
After
PR Tasks
cypress-documentation
?type definitions
?