MCP Integration Tests: Jest test runner not found
- Dominant language
- TypeScript
- Stars
- 72.6k
- Forks
- 8.6k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 85
Description
## Problem
The MCP integration tests are failing because Jest is not available in the runtime environment.
## Error Details
- Command: `npm test tests/integration/mcp.test.ts`
- Error: `jest: not found`
- Test file: `tests/integration/mcp.test.ts`
## Root Cause
Jest is listed as a devDependency in package.json but is not installed in the current environment. The test command fails immediately with "jest: not found".
## Impact
- MCP integration tests cannot be executed
- Test coverage for MCP functionality is not available
- CI/CD pipeline may be affected
## Reproduction Steps
1. Run `npm test tests/integration/mcp.test.ts`
2. Observe "jest: not found" error
## Expected Behavior
Tests should run successfully using the configured Jest test runner.
## Suggested Fix
- Ensure Jest is properly installed as a devDependency
- Verify npm install includes dev dependencies
- Consider alternative test runners if Jest installation continues to fail
## Related Files
- `tests/integration/mcp.test.ts`
- `package.json` (test scripts configuration)
---
**Backlinks:**
- PR: https://github.com/KHAEntertainment/claude-flow/pull/3
- Comment: https://github.com/KHAEntertainment/claude-flow/pull/3#issuecomment
Contributor guide
Assessment
This issue has not been assessed yet.