smoke-tests

# Running Smoke Tests Smoke tests live in `test/smoke/` and drive a full VS Code instance (Electron, web, or remote) through end-to-end user flows. ## Scripts - `npm run smoketest` — compiles the smoke tests first (`test/smoke`), then runs them. - `npm run smoketest-no-compile` — runs the already-compiled smoke tests. CI uses this after an explicit compile step. Both forward extra arguments after `--` to the runner (`test/smoke/test/index.js`). ## Common options | Option | Description | |--------|-------------| | `-g <pattern>` (alias `-f`) | Grep filter on test/suite titles (mocha `grep`). | | `--build <path>` | Run against a packaged build instead of the compiled-from-source dev build. | | `--tracing` | Capture Playwright traces (and screenshots on failure). | | `--web` | Run the browser smoke tests instead of Electron. | | `--headless` | Headless browser (used with `--web`). | | `--remote` | Run the remote smoke tests. | ```bash # Run everything (Electron, from source) npm run smoketest # Run only a subset of suites by name, with tracing (replace <suite name> with your suite, e.g. "Agents Window") npm run smoketest -- -g "<suite name>" --tracing # Run against a packaged build (CI style) npm run smoketest-no-compile -- --tracing --build "/path/to/VSCode-darwin-arm64/Code - OSS.app" ``` The `-g` pattern matches against test/suite titles. For example, `-g "Agents Window"` matches all three Agents Window suites (`Agents Window`, `Agents Window (local AgentHost)`, and...