← Back to PRs

#15569: test: comprehensive test coverage expansion (57 new test files)

by tangcruz open 2026-02-13 16:18 View on GitHub →
channel: discord channel: slack channel: telegram channel: whatsapp-web gateway channel: feishu stale size: XL
## Summary Adds 57 new test files covering modules that previously had little or no test coverage. **All tests are pure additions — zero source file changes.** ### Modules covered | Area | Test files | |------|-----------| | auto-reply | block-reply coalescer, config values, directives, inbound dedup/sender-meta/text, reply payloads, templating | | channels | allowlist matching, resolve utils, media limits, feishu normalization, sender labels | | config | agent limits, group policy, markdown tables, merge-patch, port defaults, version comparison, workspace schemas | | gateway | device auth, HTTP utils | | infra | backoff, bonjour errors, canvas host URL, errors, exec safety, format duration, heartbeat events, outbound adapters/directory cache, ports format, provider usage, WebSocket | | misc | link understanding, logging levels, markdown parsing, media constants, memory status, Slack token, Telegram updates/captions, terminal ANSI/note, TUI fuzzy filter, utils (directive tags, queue helpers, shell argv, time format), web vcard | ## Test plan - [ ] All 57 test files pass with \`vitest\` - [ ] No source files modified — zero risk of behavioral regression Generated with [Claude Code](https://claude.com/claude-code) <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR adds 57 comprehensive test files covering previously untested modules across auto-reply, channels, config, gateway, infra, and utility functions. Tests demonstrate solid engineering practices with clear naming, good edge case coverage, and appropriate use of Vitest features. **Key strengths:** - Pure test additions with zero source code modifications, eliminating regression risk - Well-structured tests following consistent patterns (descriptive names, comprehensive edge cases) - Proper use of Vitest utilities including mocking (`vi.useFakeTimers`), type assertions, and structured test suites - Tests cover important security-critical code like `exec-safety.ts` and configuration parsing **Critical issue:** - `src/config/workspace-schemas.test.ts` references non-existent data files (`workspace/data/narrative-variants.json` and `workspace/data/warroom_dashboard_config.json`), which will cause test failures <h3>Confidence Score: 3/5</h3> - Safe to merge after fixing the workspace-schemas test file issue - Score reflects the high quality of test additions (pure additions with no source changes, comprehensive coverage, good patterns) but reduced due to one test file that will definitively fail because it references non-existent data files. After fixing that single test file, this would be a 5/5. - src/config/workspace-schemas.test.ts requires immediate attention - references non-existent workspace data files <sub>Last reviewed commit: a786e14</sub> <!-- greptile_other_comments_section --> <!-- /greptile_comment -->

Most Similar PRs