Skip to content

test(mcp): prove tracedecay_health behavior - #1641

Merged
ScriptedAlchemy merged 3 commits into
masterfrom
cursor/prove-tracedecay-health-behavior-a77b
Sep 19, 2026
Merged

ScriptedAlchemy merged 3 commits into
masterfrom
cursor/prove-tracedecay-health-behavior-a77b

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Sep 18, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Prove tracedecay_health through the production MCP tools/call path on a two-file fixture, not by checking that fields exist.
  • Default markdown and format: json both report quality signal 8706 for two isolated modules ((1/2)^(1/5) * 10000). Markdown emits scalar fields in key order: files_analyzed then quality_signal.
  • path: src/left.rs reports 0 (one component, modularity 0). path: src/missing reports 10000 and files_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.rs

Test 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:** 2 then **quality_signal:** 8706; the rest of the score assertions matched on the rerun.
  • No production code change
  • The test issues the same tools/call a host uses (tracedecay_health with {}, format=json, one-file path, and a missing path)

Checklist

  • No secrets, credentials, or .env files included
  • No changelog entry: test-only, no user-facing product change
  • Breaking changes: none
Open in Web Open in Cursor 

Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
@changeset-bot

changeset-bot Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 4d31ae1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

cursoragent and others added 2 commits September 18, 2026 07:59
Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
@ScriptedAlchemy
ScriptedAlchemy marked this pull request as ready for review September 18, 2026 08:35
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@ScriptedAlchemy
ScriptedAlchemy merged commit 12d4920 into master Sep 19, 2026
40 of 69 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants