Refactor tests into unit and integration suites #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change implements best practices for VS Code extension testing by separating unit tests (fast, no VS Code dependency) from integration tests (slower, require VS Code).
Key changes:
Code Decoupling:
src/core/config.tsto isolate pure types, constants, and logic from the VS Code-dependent configuration retrieval.src/ai/registry.tsto useimport typeforvscode, allowing it to be loaded in a standard Node.js environment.Test Reorganization:
utils.test.ts,http_error.test.ts,ai.test.ts) tosrc/test/unit/.extension.test.ts,config.test.ts) tosrc/test/integration/.Configuration:
test:unitandtest:integrationscripts topackage.json.lint-stagedto run unit tests on pre-commit for TypeScript files..vscode-test.mjsto only target integration tests..github/workflows/ci.yml) to run unit tests and integration tests as separate steps.Verification:
npm run test:unitruns successfully in <1s without launching VS Code.PR created automatically by Jules for task 11259745142441659807 started by @gasatrya