Migrate to MSTest SDK instead of expecto #212
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Building on top of the NuGet CPM branch, this migrates to the new MSTest Framework instead of Expecto. Now that the Test SDK is getting lots of investment, and runs tests in a much more debuggable manner, it is more attractive for us to use something more mainline IMO.
This probably won't build in CI until later - what I'm going for here is a 'build once on latest TFM, then test for each Runtime we care about' kind of semantic. What we have now builds and runs for each Runtime (by pinning SDKs, which won't work with CPM and other tech).