Skip to content

docs: require installed cli entrypoint verification #162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bingran-you merged 1 commit into from
Apr 9, 2026
+1 −0
Merged

docs: require installed cli entrypoint verification #162

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ...tion-guardrails/verification-and-native-test-oracles/test-framework-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,7 @@ The tree can safely claim:
- there is a script-oriented entry layer, including at least one single-file lane
- the product code is written to coexist with a Bun-flavored module-mocking environment
- the visible framework depends on more than a generic "run tests" command
- public CLI verification has to include the installed or packaged entrypoint path, not only raw source-module invocation, because wrapper/runtime dependency resolution can change dispatch and help behavior even when the underlying command implementation is nominally the same
- a shared preload or reset layer exists to clean module state between same-shard tests
- sharded execution exists, including at least one Windows-specific shard
- coverage output exists as a generated artifact, even though the exact coverage driver and thresholds remain hidden
Expand Down
Loading