Uppercase file paths in Xunit reports are changed to lowercase on case sensitive operating systems #2303
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
added 2 commits
January 25, 2022 10:38
Using system dependent file paths for XUnit reports test case filenames should logically prevent duplications and allows successfull location on every file systems
|
@jnicol31 thx looks good. Only case I have to think about it's case where no filename exists and test is assigned to TestFile 'global', if behaviour is still the same? Not sure if there is a test for 'global'? |
|
@guwirth When no filename exists, the |
|
@jnicol31 thx yes that is the case I mean. That is the open point I like to verify. Rest looks good! |
guwirth
approved these changes
Jan 25, 2022
|
@guwirth You're welcome. Thanks a lot for your support and your responsiveness ! |
guwirth
changed the title
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.
Hello,
This pull-request should hopefully close #2302.
Comments are welcome !
Regards.
This change is