Summary
Tests are currently disabled in the CI pipeline (ci.yml:84) with a TODO: Re-enable tests once test suite is stabilized. This means PRs merge without any automated test validation, giving false confidence in code quality.
Problem
- CI tests disabled — The test job in
.github/workflows/ci.yml (line 84) is commented out
- SDK wrapper tests broken — Two test blocks in
packages/sdk-wrapper/src/__tests__/LighthouseAISDK.test.ts are skipped:
- Line 51:
TODO: Fix authentication mocking - tests require proper fetch/auth mock setup
- Line 83:
TODO: Fix fs mock - missing readFileSync and other fs methods
- No test gate on PRs — Branch protection has no passing test requirement
Acceptance Criteria
Files to Modify
.github/workflows/ci.yml (line 84–104)
packages/sdk-wrapper/src/__tests__/LighthouseAISDK.test.ts
- Possibly
apps/mcp-server/vitest.config.ts for coverage thresholds
Context
- MCP server uses Vitest (85% line / 90% function / 85% branch targets)
- All other packages use Jest with
ts-jest
- 47 test files exist across the codebase — most pass individually but CI integration is broken
Summary
Tests are currently disabled in the CI pipeline (
ci.yml:84) with aTODO: Re-enable tests once test suite is stabilized. This means PRs merge without any automated test validation, giving false confidence in code quality.Problem
.github/workflows/ci.yml(line 84) is commented outpackages/sdk-wrapper/src/__tests__/LighthouseAISDK.test.tsare skipped:TODO: Fix authentication mocking - tests require proper fetch/auth mock setupTODO: Fix fs mock - missing readFileSync and other fs methodsAcceptance Criteria
ci.ymlFiles to Modify
.github/workflows/ci.yml(line 84–104)packages/sdk-wrapper/src/__tests__/LighthouseAISDK.test.tsapps/mcp-server/vitest.config.tsfor coverage thresholdsContext
ts-jest