Modified tests to use expect_slice_equal() #161
Merged
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
This exercise escaped during the Peer Review and is using `testing.expect(t, slice.equal(...))` instead of the agreed upon pattern `expect_slice_equals(t, ...)` making error messages less than informative.
|
This PR touches files which potentially affect the outcome of the tests of an exercise. This will cause all students' solutions to affected exercises to be re-tested. If this PR does not affect the result of the test (or, for example, adds an edge case that is not worth rerunning all tests for), please add the following to the merge-commit message which will stops student's tests from re-running. Please copy-paste to avoid typos. For more information, refer to the documentation. If you are unsure whether to add the message or not, please ping |
glennj
approved these changes
Jan 16, 2026
rmonnet
added a commit
to rmonnet/exercism-odin
that referenced
this pull request
Jan 16, 2026
After PR exercism#161, I went through all the published exercises and checked if any other was using the 'slice.equal()' to compare expected vs result. I found another two and confirmed that the failed test report were confusing ('expected true but got false').
glennj
pushed a commit
that referenced
this pull request
Jan 17, 2026
After PR #161, I went through all the published exercises and checked if any other was using the 'slice.equal()' to compare expected vs result. I found another two and confirmed that the failed test report were confusing ('expected true but got false').
rmonnet
added
x:action/improve
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.
This exercise escaped during the Peer Review and is using
testing.expect(t, slice.equal(...))instead ofthe agreed upon pattern
expect_slice_equals(t, ...)making error messages less than informative.