Repository navigation
test: gate critical runtime coverage and hardening for 0.5.0 - #767
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Critical DOM, SSR, data and router code had no aggregate coverage measurement or regression floors. Add one V8 run across the existing unit, jsdom and Chromium projects, enforce independently measured directory floors, and retain JSON/HTML source reports in CI and the three-OS main matrix. The same command is part of the complete release gate.
Nine added cases and an extended portal assertion exercise mutating namespace/style rollback, failed cleanup during pending query/mount work, synchronous SSR cleanup aggregation, missing-node rejection/retry, and cleanup after committed portal mismatch diagnostics. The executed matrix also records existing query-generation, stale-navigation, multi-root and hydration regressions without duplicating them. Production source and public exports are unchanged.
Validation: complete
npm run checkand format checks pass: 454 unit, 98 repository, 2,706 jsdom, 158 browser and 12 installed type cases, plus public types, build, publint and package artifacts. The aggregate passes all 3,318 runtime cases. A full negative control passes those same cases and then rejects all four temporary 100% line thresholds; configured floors remain derived from the initial baseline. Final branch coverage is DOM 1307/1450, SSR 688/803, data 557/631 and router 1251/1436. Firefox/WebKit remain separate behavioral gates because V8 coverage requires Chromium.The dated readiness inventory records the merged navigation refactor and 37 remaining scoped issues before this PR. This does not qualify the complete packed 0.5 package set or publish a release.
Closes #743.
Closes #748.