fix: improve host coverage setup and missing-data reporting - #81
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.
The host coverage runner could fail before npm tests started when dependencies were absent, and it reported passing test-only suites as coverage failures. Bootstrap locked npm dependencies when node_modules is absent, record install outcomes, and display passing runs without measured coverage as ok_no_coverage. Target the tool-images registry API for coverage.
Validation: 7 focused backend regression tests passed with coverage disabled; Python syntax and git diff checks passed. Host verification passed for TES, workflow-bundles, Studio, and dev-docker. The focused backend tests do not directly exercise all script paths.
Limitations: no-coverage runs do not supply a coverage percentage; passing tests can still have a failed editable install recorded separately. Workbench failures remain unresolved. This change does not establish complete ecosystem coverage.