Improve error message on test failures #33
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
By using `expect` and `assert_eq!` instead of `assert_matches!`, the values of the expected and actual results will be printed in the panic message making it a lot easier to debug. Applying `#[track_caller]` to all the assertion functions makes the panic messages point to the place where they were called, not to within the assertion function itself. This is a lot more useful.
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.
By using
expectandassert_eq!instead ofassert_matches!, thevalues of the expected and actual results will be printed in the panic
message making it a lot easier to debug.
Applying
#[track_caller]to all the assertion functions makes thepanic messages point to the place where they were called, not to within
the assertion function itself. This is a lot more useful.