IW-613: Make non-final negated BATS assertions fail the test #647
No reviewers
Labels
No labels
agent-ready
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-human
needs-input
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/iw-cli!647
Loading…
Reference in a new issue
No description provided.
Delete branch "IW-613"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Five BATS assertions used a negated command (
! <cmd>) in a non-final position. Bash does not applyerrexitto a pipeline that starts with!, so bats could not fail the test at that line. The assertions were vacuous.Defects fixed
|| falseto each non-final negated assertion:test/help-intercept.bats:114and:189test/rm.bats:61test/open.bats:53test/contract/mill_contract.bats:62Testing
negation-repro.bats) confirmed the root cause before the fix.help-intercept.bats:114stayed green.help-intercept.bats16/16,rm.bats2/2,open.bats1/1,contract/mill_contract.bats6/6.Release notes
See
project-management/issues/IW-613/release-notes.md(Czech). Test-only change; no user-visible behavior changes.🤖 Generated with Claude Code
Closes #613
Issue: IW-613 Phase: 1 - Negated commands in a non-final position do not fail the test This commit marks the checkpoint for phase 1 context generation. Use dx-fix IW-613 to return to this point. 🤖 Generated with Claude Code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>Negated commands in a non-final position do not fail the test Artifacts: - phase-01-tasks.md 🤖 Generated with Claude Code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>