feat: add Jest unit tests and Playwright e2e test suite

[Copilot]

Introduces a modular test suite covering main-process managers (unit) and full app launch/navigation (e2e). Runs automatically on PRs targeting dev and main.

Unit Tests (Jest + ts-jest) — 76 tests

• Mocks: manual mocks for electron (safeStorage, app, BrowserWindow, ipcMain, etc.) and electron-store (in-memory Map) so tests run in plain Node.js
• Coverage: SettingsManager, InstallIdManager, EncryptionManager, ConnectionsManager, normalizeCspExceptionSource, toolSourceIcon utilities

E2e Tests (Playwright)

• Shared fixture in tests/e2e/fixtures.ts launches/tears down a real Electron process per test file; fixture waits for index.html URL and full load state before handing the window to tests, preventing false failures when firstWindow() returns while the BrowserWindow is still on about:blank
• app.spec.ts: window title (with 30 s assertion timeout for CI resilience), body visibility, sidebar presence, zero JS errors at startup
• navigation.spec.ts: settings and marketplace navigation; uses test.skip(condition, msg) for resilience against selector drift

Infrastructure

• jest.config.ts + playwright.config.ts + tsconfig.test.json
• tests/__mocks__/ for electron and electron-store
• .github/workflows/test.yml: two jobs (unit-tests, e2e-tests), e2e uses xvfb-run; both upload artifacts; e2e job explicitly installs the Electron binary via node ./node_modules/electron/install.js after pnpm install to ensure the binary is present in CI

New scripts

Script	Purpose
test:unit	Jest once
test:unit:watch	Jest watch
test:unit:coverage	Jest with lcov report
test:e2e	Playwright (requires prior build)
test:e2e:ui	Playwright interactive UI
test	unit + e2e

---

• Use a meaningful title for the pull request.
• ] Follow the guidelines from the [CONTRIBUTING.md.
• Mention the bug or the feature number the PR will be targeting.
• Test the change in your own code. (Compile and run)
• Resolve all GH Copilot comments.

[Power-Maverick]

@copilot two tests failed but they shouldnt

[electron] › tests/e2e/app.spec.ts:13:9 › App launch › main window is visible after launch ─────
[electron] › tests/e2e/app.spec.ts:22:9 › App launch › sidebar navigation is present ───────────

Make sure either the tests are written correctly or code needs fixing

[github-actions]

Bundle Size Report 📦

Bundle	Size
Main Process	965.03 KB
Renderer JS	550.26 KB
Renderer CSS	96.82 KB
Total	1.57 MB

Bundle Analysis Reports

The detailed bundle analysis reports are available in the workflow artifacts:

• 📊 Main Process: stats-main.html
• 📊 Renderer Process: stats-renderer.html

Download the artifacts from the workflow run to view interactive visualizations.

---

Bundle size tracking is now active! This helps prevent bundle bloat.

[github-actions]

Bundle Size Report 📦

Bundle	Size
Main Process	965.03 KB
Renderer JS	550.26 KB
Renderer CSS	96.82 KB
Total	1.57 MB

Bundle Analysis Reports

The detailed bundle analysis reports are available in the workflow artifacts:

• 📊 Main Process: stats-main.html
• 📊 Renderer Process: stats-renderer.html

Download the artifacts from the workflow run to view interactive visualizations.

---

Bundle size tracking is now active! This helps prevent bundle bloat.

[Copilot]

@copilot two tests failed but they shouldnt

[electron] › tests/e2e/app.spec.ts:13:9 › App launch › main window is visible after launch ─────
...

The root cause was a timing race in the window fixture.

electronApp.firstWindow() returns as soon as the BrowserWindow object is created, which can be before Electron's loadFile() has started navigating to index.html. At that moment the page is still on about:blank, and waitForLoadState("domcontentloaded") returns immediately (because about:blank's DOM is already loaded). Both failing assertions then run against an empty page with no title and no DOM.

Fixes (commit fix(e2e): wait for index.html URL before asserting on window state):

1. tests/e2e/fixtures.ts — replaced waitForLoadState("domcontentloaded") with waitForURL(/index\.html/, { timeout: 30_000 }) + waitForLoadState("load"). This guarantees the fixture only resolves after the renderer HTML and all its CSS/JS resources are fully loaded.

2. tests/e2e/app.spec.ts — added { timeout: 30_000 } to toHaveTitle for extra CI resilience (the improved fixture already handles the timing, but a generous assertion timeout prevents false negatives on slow runners).

[github-actions]

Bundle Size Report 📦

Bundle	Size
Main Process	965.03 KB
Renderer JS	550.26 KB
Renderer CSS	96.82 KB
Total	1.57 MB

Bundle Analysis Reports

The detailed bundle analysis reports are available in the workflow artifacts:

• 📊 Main Process: stats-main.html
• 📊 Renderer Process: stats-renderer.html

Download the artifacts from the workflow run to view interactive visualizations.

---

Bundle size tracking is now active! This helps prevent bundle bloat.

[Power-Maverick]

@copilot the test CI process failed

[Copilot]

@copilot the test CI process failed

The CI failure was caused by the Electron binary not being downloaded in the e2e job. pnpm install runs electron's postinstall script but it can fail silently in CI environments, leaving the binary absent. Playwright then throws Electron failed to install correctly when it tries to launch.

Fixed in commit fix(ci): explicitly install Electron binary in e2e workflow by adding an explicit step after pnpm install:

- name: Install Electron binary
  run: node ./node_modules/electron/install.js

This ensures the binary is always present before Playwright attempts to launch the app.

[github-actions]

Bundle Size Report 📦

Bundle	Size
Main Process	965.03 KB
Renderer JS	550.26 KB
Renderer CSS	96.82 KB
Total	1.57 MB

Bundle Analysis Reports

The detailed bundle analysis reports are available in the workflow artifacts:

• 📊 Main Process: stats-main.html
• 📊 Renderer Process: stats-renderer.html

Download the artifacts from the workflow run to view interactive visualizations.

---

Bundle size tracking is now active! This helps prevent bundle bloat.