test(cli): add command path coverage#16
Merged
Merged
Conversation
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
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.
What changed
Added CLI command tests for existing command paths: no-argument help,
scan --help,--version, and unknown command handling.Why
These paths are part of the public CLI contract but were not directly covered by tests. The added coverage makes command behavior safer to maintain as argument parsing changes.
Testing
npm.cmd run buildnpm.cmd testThe two
Error:lines are expected stderr output from CLI error-path tests.npm.cmd run lintRisks
None identified.
Follow-up
Fix the stale README configuration section so it reflects existing
opk.config.jsonsupport.