Migrate to xunit.v3 #17250
Merged
Migrate to xunit.v3 #17250
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
|
Is this related to the new features in https://xunit.net/docs/getting-started/v3/whats-new ? Or are there particular reasons for this PR? |
|
@hishamco I updated the PR description with the initial goal. |
This was referenced Jan 1, 2025
|
FYI Renovate will open PRs about updating |
|
What's remaining here? |
gvkries
approved these changes
Jan 16, 2025
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Investigating the impact of updating to xunit.v3. Locally it's the same perf. Not sure if the VS integration is better.
Worst case scenario we are following the main branch.