feat(assert): test interactive prompt commands via assert_exec#633
Merged
Chemaclass merged 2 commits intomainfrom Apr 19, 2026
Merged
feat(assert): test interactive prompt commands via assert_exec#633Chemaclass merged 2 commits intomainfrom
Chemaclass merged 2 commits intomainfrom
Conversation
Add --stdin, --stdout-contains, --stdout-not-contains, --stderr-contains and --stderr-not-contains flags to assert_exec so interactive commands that read from stdin can be exercised from tests and output can be asserted via substring match. Closes #301
JesusValeraDev
approved these changes
Apr 19, 2026
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
2 participants
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.
🤔 Background
Related #301
Bashunit had no idiomatic way to drive commands that read from stdin (interactive prompts). This extends the existing
assert_execprimitive so the Laravel-styleexpectsQuestion/expectsOutput/doesntExpectOutput/assertExitCodeflow can be expressed in a single call.💡 Changes
--stdinflag toassert_execto pipe input into the command under test--stdout-contains/--stdout-not-contains/--stderr-contains/--stderr-not-containsfor substring assertions on captured outputassert_advanced_test.shdocs/assertions.mdand refresh thebashunit docsnapshot