Skip to content

ci: run the JS (Vitest) suite in the Unit Tests workflow - #347

Merged
jqnatividad merged 1 commit into
mainfrom
ci-js-tests
Oct 9, 2026
Merged

jqnatividad merged 1 commit into
mainfrom
ci-js-tests

Conversation

@jqnatividad

Copy link
Copy Markdown
Collaborator

Why

The 12 Vitest tests under tests/js/ pin the polling contract between scheming-ai-suggestions.js and the Python pipeline, but no workflow ran them. Dependabot's npm bumps (#333, #339) were only checked because someone ran npm test by hand.

What

A js-tests job in test.yml (the Unit Tests workflow), running alongside the Python unit suite on the same triggers:

  • Node 22, the current LTS (vitest 4 supports Node 20, 22 and 24 or later)
  • actions/setup-node@v4 with npm caching
  • npm ci, then npm test

Verification

  • npm ci && npm test locally: 12/12 pass.
  • actionlint is clean.
  • This PR's own run is the first CI run of the job.

🤖 Generated with Claude Code

The 12 tests under tests/js/ pin the polling contract between
scheming-ai-suggestions.js and the Python pipeline, but no workflow ran them,
so Dependabot's npm bumps (vitest, jsdom, jquery) merged unchecked. Adds a
js-tests job (Node 22, npm ci + npm test) alongside the Python unit suite.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jqnatividad
jqnatividad merged commit 52a6e59 into main Oct 9, 2026
3 checks passed
@jqnatividad
jqnatividad deleted the ci-js-tests branch October 9, 2026 01:11
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