Build script - now using xUnit #62
Merged
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
andrewtobin
added a commit
that referenced
this pull request
Jan 15, 2012
Build script - now using xUnit There is one failing test but the xUnit works - merging because it should be up to test author to fix.
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.
After some chatter around being able to test the code quickly, I've put together a simple process that we can all use to verify the current code.
How?
Open a command prompt and navigate to the project root and run
.\build.cmdWhat's happening?
This will compile the code using MSBuild and run the tests using the xUnit console test runner.
Adding tests
We are currently using xUnit and Moq in our unit tests. If you would like to see something else being used for Code52 drop into the JabbR room to discuss.
Note that we need a tool which: