Skip to content

✅ test: add test suites for mq-web, mq-playground, and vscode extension#1986

Merged
harehare merged 2 commits into
mainfrom
chore/typescript-7-and-tests
Jul 10, 2026
Merged

✅ test: add test suites for mq-web, mq-playground, and vscode extension#1986
harehare merged 2 commits into
mainfrom
chore/typescript-7-and-tests

Conversation

@harehare

Copy link
Copy Markdown
Owner

Summary

Also upgrade typescript to v7 (^7.0.2) across mq-web, mq-nodejs, mq-playground, and editors/vscode. mq-web, mq-playground, and the vscode extension had zero test coverage, so add it while verifying the upgrade:

  • mq-web: vitest suite mirroring mq-nodejs's API tests, using a fetch shim so the wasm-pack "web" target binary loads under Node.
  • mq-playground: vitest + React Testing Library covering device detection, the OPFS file system wrapper, ConfirmDialog, and Toast.
  • editors/vscode: wire up the previously-unused @vscode/test-cli / @vscode/test-electron scaffolding into a working integration harness that runs against a real VS Code Extension Host.
  • mq-playground/pnpm-workspace.yaml: exclude typescript/@typescript/* from the 3-day minimumReleaseAge policy so 7.0.2 can install.

Type of Change

  • 🐛 Bug fix
  • ✨ New feature
  • ♻️ Refactor
  • 📝 Documentation
  • ⚡ Performance
  • ✅ Test
  • 📦 Build / dependencies
  • 👷 CI

Checklist

  • I ran cargo fmt and cargo clippy and addressed any warnings
  • I ran just test-all and all tests pass
  • I added or updated tests covering this change
  • I updated relevant documentation (/docs, crate README.md) if needed
  • I added a changelog entry if this is a user-facing change

Additional Context

harehare added 2 commits July 10, 2026 22:27
Also upgrade typescript to v7 (^7.0.2) across mq-web, mq-nodejs,
mq-playground, and editors/vscode. mq-web, mq-playground, and the
vscode extension had zero test coverage, so add it while verifying
the upgrade:

- mq-web: vitest suite mirroring mq-nodejs's API tests, using a
  fetch shim so the wasm-pack "web" target binary loads under Node.
- mq-playground: vitest + React Testing Library covering device
  detection, the OPFS file system wrapper, ConfirmDialog, and Toast.
- editors/vscode: wire up the previously-unused @vscode/test-cli /
  @vscode/test-electron scaffolding into a working integration
  harness that runs against a real VS Code Extension Host.
- mq-playground/pnpm-workspace.yaml: exclude typescript/@typescript/*
  from the 3-day minimumReleaseAge policy so 7.0.2 can install.
Command IDs were duplicated between package.json's contributes.commands
and the extension test's hardcoded EXPECTED_COMMANDS array, so adding a
new command without registering it (or vice versa) could go unnoticed.
Read the declared commands from the extension's packageJSON at runtime
instead, keeping only the 4 commands intentionally left out of
contributes.commands (status-bar-only, not in the Command Palette) as
an explicit list.
@harehare
harehare merged commit ad95d15 into main Jul 10, 2026
9 checks passed
@harehare
harehare deleted the chore/typescript-7-and-tests branch July 10, 2026 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant