Add new assert_exec #469
Merged
Add new assert_exec #469
Conversation
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
Chemaclass
force-pushed
the
feat/466-assert-exec
branch
from
c0e00a5 to
256f1d2
Compare
JesusValeraDev
approved these changes
Aug 3, 2025
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.
📚 Description
Related #466
🔖 Changes
Introduced a new assert_exec helper that executes a command, captures exit status, stdout, and stderr, and validates all expectations together for concise command checks
Added unit tests demonstrating successful and failing scenarios for assert_exec, ensuring coverage of exit codes and output assertions
Documented assert_exec usage and options in the assertions guide so users can quickly adopt the new helper
Updated the changelog to highlight the new consolidated execution assertion in the unreleased notes
✅ To-do list
CHANGELOG.mdto reflect the new feature or fix