MCP Integration Tests: Jest test runner not found
Author: coderabbitai[bot]Created Sep 5, 2025Updated Sep 16, 2026
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
- Run
npm test tests/integration/mcp.test.ts - 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.tspackage.json(test scripts configuration)
Backlinks:
Source: ruvnet/ruflo