Add new context and make integration tests stricter #321
Conversation
This file contains 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
I added a new context and I noticed that the tests were still passing Turns out the `.Contains` condition on the output was still matching I changed to a strict `Equal` and remove the stderr output from there The subpath image is unused so far, but it will be in a future PR
malcolmholmes
approved these changes
Feb 1, 2024
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.
I added a new context and I noticed that the tests were still passing (incorrectly)
Turns out the
.Containscondition on the output was still matching. I changed to a strictEqualand removed the stderr output from there. We're not trying to match log lines hereThe subpath context is unused so far, but it will be in a future PR