test(mcp): prove tracedecay_health behavior - #1641
Merged
ScriptedAlchemy merged 3 commits intoSep 19, 2026
Merged
Conversation
Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
|
Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
ScriptedAlchemy
marked this pull request as ready for review
September 18, 2026 08:35
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Summary
tracedecay_healththrough the production MCPtools/callpath on a two-file fixture, not by checking that fields exist.format: jsonboth report quality signal 8706 for two isolated modules ((1/2)^(1/5) * 10000). Markdown emits scalar fields in key order:files_analyzedthenquality_signal.path: src/left.rsreports 0 (one component, modularity 0).path: src/missingreports 10000 andfiles_analyzed: 0.Motivation
The existing health handler test only checks that detail keys are present. That still passes when every score is wrong. This pins the scores a caller actually observes.
Changes
crates/tracedecay/tests/mcp_suite/mcp_handler_test/health_behavior_test.rsTest plan
scripts/require-exact-test.sh cargo test -p tracedecay --test mcp_suite --features test-transport mcp_handler_test::health_behavior_test::health_scores_two_isolated_modules_and_distinguishes_scope -- --exact— 1 passed. First run observed markdown**files_analyzed:** 2then**quality_signal:** 8706; the rest of the score assertions matched on the rerun.tools/calla host uses (tracedecay_healthwith{},format=json, one-file path, and a missing path)Checklist
.envfiles included