Fix: Prevent Storybook UI HTML from polluting testing-library error messages#34120
Draft
Fix: Prevent Storybook UI HTML from polluting testing-library error messages#34120
Conversation
… testing-library errors Co-authored-by: valentinpalkovic <5889929+valentinpalkovic@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix poorly formatted HTML in Storybook errors
Fix: Prevent Storybook UI HTML from polluting testing-library error messages
Mar 12, 2026
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
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.
When
screenqueries fail (e.g.,screen.getByText('...')),@testing-library/dom's defaultgetElementErrorcallsprettyDOM(container)wherecontainerisdocument.body. In Storybook,document.bodycontains the full Storybook UI markup, producing hundreds of lines of irrelevant HTML that buries the actual error.Changes
code/core/src/test/testing-library.ts: Configure a customgetElementErrorviadomTestingLibrary.configure()that skips theprettyDOMdump whencontainer === document.body, while still including it for scoped containers (e.g., storycanvaselement).This means errors from
screenqueries show only the relevant message, while errors fromcanvas/withinqueries still include the scoped DOM snapshot.Original prompt
This section details on the original issue you should resolve
<issue_title>Poorly formatted HTML is inserted into Storybook errors, hiding real issues and filling the console with noise</issue_title>
<issue_description>
Discussed in #34118
Originally posted by rschristian March 12, 2026
Summary
Every time a Storybook test fails, we get error messages like the following printed to the console. I've pasted the whole thing exactly as it is output: