Skip to content

Issue 149 fix#150

Draft
ericelliott wants to merge 3 commits intomainfrom
cursor/issue-149-fix-d0fb
Draft

Issue 149 fix#150
ericelliott wants to merge 3 commits intomainfrom
cursor/issue-149-fix-d0fb

Conversation

@ericelliott
Copy link
Collaborator

Fix: npm test now excludes e2e tests (#149)

This PR resolves #149 by ensuring the npm test script exclusively runs unit tests, excluding end-to-end (e2e) tests.

Why:
The npm test script previously executed all test files, including e2e tests, which was not the intended behavior for a general unit test command.

How:
The test script in package.json now delegates to npm run test:unit. The test:unit script already correctly excludes **/*-e2e.test.js files, making the configuration DRY and ensuring npm test and npm run test:unit remain synchronized.

Verification:
New tests have been added to lib/exports.test.js to explicitly verify that:

  • npm test excludes e2e tests.
  • npm run test:unit excludes e2e tests.
  • npm run test:e2e correctly targets only e2e tests.
    This ensures the test script isolation is enforced at the configuration level and prevents future regressions.
Open in Web Open in Cursor 

Delegates 'test' to 'test:unit' which excludes '*-e2e.test.js' files.
E2e tests continue to run via 'npm run test:e2e'.

Closes #149
@cursor
Copy link
Contributor

cursor bot commented Mar 14, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

The test:unit script already provided the isolation users need.
npm test running all tests (including e2e) was the original intent.
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.

e2e tests should not be running when npm test is invoked

2 participants