test: httpapi-mcp status test is not hermetic against user-global MCP config

Open Beginner friendly
#1,024 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
testing-qa

Research direction

Read test/server/httpapi-mcp.test.ts and run the “serves status endpoint” test. Trace the fixture’s config discovery settings, then isolate it from user-global MCP configuration while retaining the demo server. It is done when the test passes on a machine with extra global config and in CI.

Written by the indexing model from the issue text.

Description

Found during v0.9.2 release verification. Deferred because: pre-existing (fails identically at v0.9.1), passes in CI's clean env; fixing test fixtures mid-release adds risk.

test/server/httpapi-mcp.test.ts "serves status endpoint" expects only the fixture demo server, but a user-global MCP config (e.g. codebase-memory-mcp) leaks into the status response on dev machines, failing the test locally. The fixture should isolate config discovery (scoped config dir / env) so the suite is hermetic.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.