Use less ambiguous string representations in equality errors #368
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
`toString` produces ambiguous results for a number of common types. For example: ```kotlin "1" shouldBe 1L ``` ``` expected: 1 but was: 1 ``` or ```kotlin listOf(1f) shouldBe listOf(1.0) ``` ``` expected: [1.0] but was: [1.0] ``` etc. This PR formats objects the way their literal values appear in code. e.g. ``` expected: "1" but was: 1L ``` Now that the representations are less ambiguous, we can use the JUnit assertions for all types.
|
Awesome! |
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.
toStringproduces ambiguous results for a number of common types. For example:or
etc.
This PR formats objects the way their literal values appear in code.
e.g.
Now that the representations are less ambiguous, we can use the JUnit assertions for all types.