test: use native assert_stderr - #533
Merged
Merged
Conversation
nieomylnieja
changed the title
nieomylnieja
enabled auto-merge (squash)
August 26, 2026 13:53
nieomylnieja
disabled auto-merge
August 27, 2026 07:45
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
1 participant
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.
Motivation
The Bats image bundles a
bats-assertversion withoutassert_stderr, so the test suite maintained a copied wrapper. That wrapper replaced captured stdout with stderr and broke tests that checked both streams.Summary
Pinned
bats-assert2.2.4 in the unit and end-to-end test images and removed the copied wrapper. The native assertion reads stderr without changing the captured stdout.Testing
Verified in the rebuilt test image that native
assert_stderrvalidates stderr while a followingassert_outputstill receives the original stdout.