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
- Add comprehensive tests for makeCoderSdk, createStreamingFetchAdapter, and waitForBuild- Refactor stream event handlers into testable setupStreamHandlers function- Set up code coverage analysis with vitest and @vitest/coverage-v8- Add coverage commands: yarn test:coverage and yarn test:coverage:ui- Update test count from 59 to 105 tests (102 -> 105 with new handler tests)- Achieve 100% line coverage, 100% function coverage for api.ts- Update CLAUDE.md to always use CI test mode and document coverage commands- Configure vitest.config.ts with coverage thresholds and reporting🤖 Generated with [Claude Code](https://claude.ai/code)Co-Authored-By: Claude <noreply@anthropic.com>
6.**`waitForBuild()`** ✅ - Build monitoring and log streaming
65
+
- ✅ Test initial log fetching
66
+
- ✅ Test WebSocket connection for follow logs
67
+
- ✅ Test log streaming and output formatting
68
+
- ✅ Test WebSocket error handling
69
+
- ✅ Test build completion detection
70
+
- ✅ Mock WebSocket and API responses
71
+
72
+
**Note:** Helper functions`getConfigString()` and`getConfigPath()` are internal and tested indirectly through the public API functions.
69
73
70
74
**Test Infrastructure Needs:**
71
75
- Mock VSCode workspace configuration
@@ -201,4 +205,4 @@ This document outlines the comprehensive testing improvements needed for the VSC
201
205
202
206
---
203
207
204
-
**Next Action:**Start with`src/api.test.ts`implementation focusing on the`needToken()` and`createHttpAgent()` functions first.
208
+
**Next Action:**✅ COMPLETED -`src/api.test.ts`now has comprehensive test coverage with 43 tests covering all exported functions. Next priority: Start implementing tests for`src/api-helper.ts` andother untested modules.