You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test: CI coverage gate, harden command assertions, injectable health timeout
- Enforce coverage thresholds in CI (npm run test:coverage)
- Replace 12 bare .toHaveBeenCalled() in commands.test.ts with specific checks
- Add healthCheckTimeout to CustomConfig (default 5s, injectable for tests)
- Custom backend test suite drops from ~5.2s to ~0.4s
# Test Suite Review V2 — Combined Findings (2026-02-20)
2
+
3
+
## Documents Merged
4
+
5
+
-`a1b2c3-test-suite-review.md`
6
+
-`test-suite-review-2026-02-20-a7k3p9.md`
7
+
8
+
## Executive Summary
9
+
10
+
The test suite is already strong and well-structured, with high coverage and stable green runs. The highest-value improvements are not broad rewrites, but targeted hardening in four areas: CI quality gates, assertion precision, slow timeout-path tests, and selected uncovered orchestration/platform branches.
11
+
12
+
## Current State Snapshot
13
+
14
+
- Test files: 16
15
+
- Tests: 245
16
+
- Status: 245/245 passing
17
+
- Runtime: ~5.5s
18
+
- Coverage:
19
+
- Statements: 95.64%
20
+
- Branches: 87.12%
21
+
- Functions: 93.79%
22
+
- Lines: 97.05%
23
+
24
+
## Consolidated Strengths
25
+
26
+
- Clear module-based test organization (commands, setup, provider, chunker, backends).
27
+
- Good mix of unit and integration-style tests.
28
+
- Existing coverage of cancellation/error behavior in critical paths.
29
+
- Extension workflow behaviors are exercised via VS Code mocks.
30
+
31
+
## Consolidated Gaps
32
+
33
+
### 1) CI Gate Incomplete (Process Risk)
34
+
35
+
- CI currently runs tests/build/typecheck but does not enforce coverage thresholds via coverage run.
36
+
- Impact: coverage regressions can merge undetected.
37
+
38
+
### 2) Assertion Strictness (Quality Risk)
39
+
40
+
- Some tests rely on permissive assertions (for example: broad “called” checks, `>= 1` chunk expectations).
41
+
- Impact: behavior regressions may pass despite changing semantics.
42
+
43
+
### 3) Timeout Test Cost (Speed/Flake Risk)
44
+
45
+
-`customBackend` timeout-path tests consume several seconds due to real timeout waits.
46
+
- Impact: slower feedback loops and greater CI variability.
0 commit comments