Skip to content

Make foundational command behavior independently provable - #91

Open
rohoswagger wants to merge 2 commits into
mainfrom
test/small-command-coverage
Open

Make foundational command behavior independently provable#91
rohoswagger wants to merge 2 commits into
mainfrom
test/small-command-coverage

Conversation

@rohoswagger

Copy link
Copy Markdown
Owner

Part of a stack managed by ez.

Exercise amend, commit, parent, and log through real temporary repositories, including linked worktree rendering and hermetic GitHub status responses. The tests cover success, rejection, staging, JSON, and human-output control flow without changing production behavior.

Constraint: Tests must not depend on network access or mutate the developer repository.

Confidence: high

Scope-risk: narrow

Reversibility: clean

Tested: cargo llvm-cov --all-features --workspace; cargo clippy --all-targets --all-features -- -D warnings; cargo fmt --check

Not-tested: Live GitHub rendering; covered hermetically with a fake gh executable.
Add compiled-CLI assertions for nested stack JSON, worktree markers, current-branch rendering, parent stdout, and GitHub-backed PR/draft/CI fields so the coverage tests prove user-visible behavior rather than only successful control flow.

Constraint: GitHub behavior remains hermetic through a fake gh executable.

Confidence: high

Scope-risk: narrow

Reversibility: clean

Tested: cargo test --test core_cli --all-features log_and_parent_report_the_real_nested_worktree_stack; cargo test --test core_cli --all-features log_renders_pr_draft_ci_and_url_from_github_responses

Related: Independent review finding on PR #91.
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.

1 participant