test(@angular/build): temporarily disable Vitest coverage check on Windows #31845
Conversation
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
…ndows Disables the JSON coverage report assertion in the larger project E2E test when running in JSDOM mode on Windows. This is a temporary workaround to address a platform-specific issue where the `coverage-final.json` file is unexpectedly empty. The browser-mode coverage check and the JSDOM check on other platforms remain active. Further investigation is required to determine the root cause of the Windows JSDOM coverage issue.
alan-agius4
approved these changes
Nov 17, 2025
Member
Author
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.
Disables the JSON coverage report assertion in the larger project E2E test when running in JSDOM mode on Windows. This is a temporary workaround to address a platform-specific issue where the
coverage-final.jsonfile is unexpectedly empty.The browser-mode coverage check and the JSDOM check on other platforms remain active. Further investigation is required to determine the root cause of the Windows JSDOM coverage issue.