add support for running tests inside Visual Studio #939
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
|
And here's the official advice about xUnit in Visual Studio. |
nulltoken
added a commit
that referenced
this pull request
Jan 30, 2015
add support for running tests inside Visual Studio
|
💣💥🔥💨 |
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.
For the longest time, there's been a VSIX available to run your xUnit tests in VS (2012+).
Now they've switched over to using the NuGet-based option. You may think this requires upgrading to xUnit 2.0, but that's not necessary - it works with xUnit 1.0 tests as well.
This saved me a lot of time digging into the tests I was writing for #938, so hopefully it can help someone else out!
In VS2013 Update 4: