Refine case names #355
Merged
Refine case names #355
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
… serialize escape sequences.
…ie.Assertions library.
…ry optimizations do the work.
… extensions methods tend to be for broad-scope public use.
…s a common test parameter type with a natural serialization.
…ull scope of unicode escape handling or lack thereof can be witnessed at once instead of one special character at a time, and to reduce the risk of the old brittle helper unintentionionally failing to inspect some items (which wasn't happening but easily could).
…aracters and whitespace characters when serializing char/string paramters in case names.
… serializing char/string parameters in case names.
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.
This improves the handling of C# values serialized when building the name of a parameterized case, based on lessons learned during the development of rich serialization in the separate Fixie.Assertions repo.
\uxxxxfour-digit unicode escape sequences are used for all control characters and whitespace characters that do not already have a more terse unambiguous representation in char/string literals. Single-character escape sequences and the literal space " " take precedent, otherwise control/whitespace characters appear with\uxxxxformat.