Testing Commands

Info

This document covers Vitest commands for running, filtering, and measuring test coverage, plus Playwright commands for Electron E2E testing.

All commands are run from the eIsland project root, where package.json and vitest.config.ts are located:

npm run <script>

npm run test

Runs both the node and renderer test projects once.

npm run test

Configuration: Vitest 4.1.10 with:

• environment: 'node'
• clearMocks: true — mocks are cleared between tests
• restoreMocks: true — mocks are restored to their original implementation
• Two named projects, both inheriting the root configuration with extends: true
• Support for both .test.ts and .test.tsx files

Project	Test File Pattern	Exclusion	CLI Label Color
node	src/**/*.test.{ts,tsx}	src/renderer/**	Yellow
renderer	src/renderer/**/*.test.{ts,tsx}	None configured	Magenta

Important

The node and renderer labels identify test projects. Both currently run in the Node.js environment; naming a project renderer does not provide a DOM or launch Electron. Tests that require DOM interaction need a configured environment such as jsdom or happy-dom and its dependency.

Latest Verified Test Run

The full suite passed on 2026-10-05:

Project	Test Files	Passing Tests
node	59	778
renderer	138	1913
Total	197	2691

These counts describe the Vitest application suite; Electron E2E and native plugins have separate test configurations.

Tips

For iterative development, use npx vitest (without run) to start Vitest in watch mode — it re-runs affected tests on file save.

When to use:

• Before committing code
• In CI pipelines
• After pulling new changes to verify nothing is broken

npm run test:node

Runs only the node project, which collects tests under src/ outside src/renderer/, including main process and preload tests.

npm run test:node

Under the hood: vitest run --project node

npm run test:renderer

Runs only the renderer project for renderer stores, utilities, hooks, and component tests.

npm run test:renderer

Under the hood: vitest run --project renderer

Tips

Filter a project to a specific test file by forwarding its path through npm:

npm run test:renderer -- src/renderer/components/states/questionnaire/components/test/QuestionnaireQuestion.test.ts

npm run test:preload

Runs only the preload bridge test file.

npm run test:preload

Under the hood: vitest run src/preload/index.test.ts

Note

This is a subset of npm run test. Use it when modifying preload code for faster feedback — it skips all other test files.

npm run test:coverage

Runs both test projects with the V8 coverage provider (@vitest/coverage-v8).

npm run test:coverage

Output: Coverage report in the terminal and coverage/ directory with HTML reports.

When to use:

• Before opening a PR to review exercised code and untested paths
• Periodically to audit test gaps
• When adding new features to ensure they are tested

Audit Renderer TSX Coverage

Use an explicit include pattern to measure all renderer TSX source files, including files that tests do not import:

npm run test:coverage -- --coverage.include="src/renderer/**/*.tsx" --coverage.reportsDirectory=coverage/renderer-tsx

The audit on 2026-10-05 measured:

Metric	Result
.test.tsx files	0
Renderer TSX source files	278
TSX files with executed statements	15
TSX files without executed statements	263
Line coverage	2.38%
Statement coverage	2.30%
Function coverage	2.08%
Branch coverage	2.51%

Note

These percentages cover only src/renderer/**/*.tsx, not the entire application. Existing .test.ts files already exercise some TSX components through React.createElement and static rendering with react-dom/server. The absence of .test.tsx files does not mean there are no component tests; UI interaction and unexecuted component paths still need additional coverage.

Electron E2E Commands

The Playwright suite launches real Electron windows on Windows and macOS. Source, configuration, build output, and diagnostics live in the repository-root e2e/ directory.

Command	Description
npm run build:e2e	Build with --mode e2e into e2e/out/
npm run test:e2e	Build and run the Electron E2E suite
npm run test:e2e:run	Run an existing E2E build with e2e/playwright.config.ts
npm run typecheck:e2e	Check E2E TypeScript and electron.vite.config.ts

npm run typecheck:e2e
npm run test:e2e

Important

E2E requires an installed Electron binary and a graphical desktop session. The existing test, typecheck, and check scripts do not automatically run E2E. See Electron E2E Testing for dependency installation, filtering, isolation boundaries, CI, and diagnostics.

Troubleshooting

npm run test Fails After Pull

Stale build artifacts:

rm -rf out/ node_modules/
npm install
npm run test