Skip to content

test: run all test files in npm test, not just smoke tests#15

Open
dmchaledev wants to merge 1 commit into
mainfrom
claude/sleepy-rubin-QNnoB
Open

test: run all test files in npm test, not just smoke tests#15
dmchaledev wants to merge 1 commit into
mainfrom
claude/sleepy-rubin-QNnoB

Conversation

@dmchaledev

Copy link
Copy Markdown
Contributor

Problem

The npm test script only runs test/smoke.test.mjs:

"test": "node --test test/smoke.test.mjs"

That's 6 tests. But the repo also has test/calculate.test.mjs with 59 tests covering VM sizing, timing, costs, ROI analysis, recommendations, and edge cases — added in dafee26. Those 59 tests have never run in CI, even though the commit message for dafee26 stated the test script was switched to a glob (it wasn't — the script was never changed).

The net effect: ~91% of the test suite (59 of 65 tests) is silently skipped on every push and PR. The calculation engine — the actual product logic — has zero CI coverage.

Fix

Switch the test script to a glob so all test files run:

"test": "node --test test/*.test.mjs"

Verification

Before (main):

# tests 6
# pass 6

After (this PR):

# tests 65
# pass 65
# fail 0

All 65 tests pass. No source or test files were modified — this only restores the existing-but-orphaned tests to the CI run. One-line change, fully self-contained.

https://claude.ai/code/session_01BknoASdgDLN3NPV1RmoHEv


Generated by Claude Code

The npm test script only ran test/smoke.test.mjs (6 tests), so the 59
calculation tests added in dafee26 never executed in CI despite that
commit's message stating the script was switched to a glob.

Switch to test/*.test.mjs so all test files run. npm test now executes
all 65 tests (6 smoke + 59 calculation), all passing.
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.

2 participants