Make small command and defensive invariants executable - #98
Merged
Conversation
Exercise shell setup output, initialization, diff and scope behavior against real repositories while locking defensive stack, lease, and conflict-reporting paths. Constraint: Coverage tests must remain hermetic and avoid GitHub or network access. Rejected: Mock command internals | compiled CLI tests prove persisted Git and ez state more directly. Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep the temporary repositories isolated and preserve exact refusal-state assertions. Tested: cargo test --bin ez --all-features; cargo test --test small_shared_cli --all-features; cargo clippy --all-targets --all-features -- -D warnings; cargo fmt --check; git diff --check Not-tested: Windows-specific shell and file-lock behavior
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.
Summary
Verification
Tests are hermetic and make no network or GitHub calls.