Fix issue #2121 DataTestMethodAttribute is missing a constructor #2125
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
…ructor to set display name
|
@microsoft-github-policy-service agree company="Nextens" |
Evangelink
reviewed
Jan 18, 2024
Evangelink
approved these changes
Jan 19, 2024
|
Thanks for the contribution @HannoZ |
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.
A fix for issue #2121 DataTestMethodAttribute doesn't have a constructor to set display name
I added the constructor and extended the TypeEnumerator logic to get the DisplayName for DataTestMethodAttribute (only if no regular TestMethodAttribute was found)
Renamed an existing unit test for TestMethodAttribute and added a new test for DataTestMethodAttribute that verifies that the DisplayName is set.