Working isolated vsix tests by fuhrmanator · Pull Request #1 · Leoo-code/FamixTypeScriptImporter

vsix test harness and test runner for testing the packaged extension in isolation from source.

fuhrmanator

committed

remove redundant launch arguments for user data and extensions directories in test setup

fuhrmanator

committed

Truly isolated VSIX test, typescript is not externalized, and smoke tests run against the installed VSIX in a clean profile.

fuhrmanator

committed

Default import syntax in smoke test

fuhrmanator

committed

improved error handling and messaging in command execution, updated package version, and fixed VSIX file discovery logic for testing.

fuhrmanator

committed

Make sure to test the VSIX that corresponds to the current package.json version, not just the latest one in the directory. This ensures we're testing the correct build artifact.

fuhrmanator

committed

ChatGPT re-installed ts2famix to update the version used in the project -- this is tricky

fuhrmanator

committed

npm audit fix for ts2famix

fuhrmanator

committed

CI workflow updates: upgrade Node.js to 22.x and use npm ci for consistent installs.

fuhrmanator

committed

ignore test fixtures in server tsconfig

fuhrmanator

committed

prevent compilation errors due to missing express dependency in test fixture project

fuhrmanator

committed

Remove useless exclude entry from tsconfig.json

fuhrmanator

committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Working isolated vsix tests#1

Working isolated vsix tests#1
Leoo-code merged 12 commits into
devfrom
Working-isolated-VSIX-tests

Commits on Jun 4, 2026

vsix test harness and test runner for testing the packaged extension in isolation from source.

remove redundant launch arguments for user data and extensions directories in test setup

Truly isolated VSIX test, typescript is not externalized, and smoke tests run against the installed VSIX in a clean profile.

Default import syntax in smoke test

improved error handling and messaging in command execution, updated package version, and fixed VSIX file discovery logic for testing.

Make sure to test the VSIX that corresponds to the current package.json version, not just the latest one in the directory. This ensures we're testing the correct build artifact.

ChatGPT re-installed ts2famix to update the version used in the project -- this is tricky

npm audit fix for ts2famix

CI workflow updates: upgrade Node.js to 22.x and use npm ci for consistent installs.

ignore test fixtures in server tsconfig

prevent compilation errors due to missing express dependency in test fixture project

Remove useless exclude entry from tsconfig.json