fix: include adapter tests in default npm test#969
Merged
Conversation
`npm test` only ran unit + extension projects, so adapter tests (clis/**/*.test.js) were never exercised by the default test command. Add --project adapter so they run alongside unit and extension tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
npm testonly ranunit+extensionprojects, meaning adapter tests (clis/**/*.test.js) were never exercised by the default test command--project adapterto thetestscript inpackage.jsonRaised by @codex-mini1 during review of PR #967.
Test plan
npm testnow runs adapter tests (verified locally — 194 files, 1458 passed)