Added git ignore file
Cleanup and organization

Add a .gitignore. Add solution reference to nuspec file. Clean up some
tabs/spaces and newlines.
Reduce test output verbosity

To better match the expectations for NUnit test output, eliminate trace
describing passed tests when running from the NUnit console. Failed test
info will still appear in the console. Note that ReSharper will still
display the full trace for individual specs in the test results window,
which is reasonable because it will only show the output for the single
selected spec.
merge
Added SetUp and TearDown methods to specs to provide a way to run code before and after a spec is run.
Added test project with tests for SetUp and TearDown methods. Added FizzBuzz to be able to demo tests in the readme file
Fixed commenting issues to reference current naming
Renamed SetUp and TearDown to BeforeEachExample and AfterEachExample. Still have a test case that fails the before each count (commented out)
Fixed the broken tests so that BeforeEachExample and AfterEachExample are called the correct number of times.
Merge pull request #1 from RossCode/master

Add BeforeEachExample and AfterEachExample methods
Adding a spec to illustrate a (potential?) issue with nested Givens
Adding a flag to track whether or not the 'setupAction' for each context has already been run or not to avoid running them multiple times.
Removing a possibly extraneous call to 'InitializeContext' from within the recursive VerifyContexts method since we're already invoking it from within VerifySpecs. Removed the flag on context that would keep the initialize from getting called more than once.
Adding some additional tests to prove out the "nested givens" issue is resolved.
Merge pull request #3 from appakz/master

Fix for issue with nested givens having their setup actions called multiple times
Updating the assembly version and nuspec release notes for version 0.3.0.0
Merge pull request #4 from appakz/master

New version info for 0.3.0.0
Adding a simple database integration spec to illustrate how to use Before/AfterEachExample to rollback transactions and keep data in a consistent state.
Adding a spec that illustrates how to use the BeforeEachExample and AfterEachExample to test against a database where transactions need to be rolled back.
Merge pull request #5 from appakz/master

Added a spec that illustrates how to test against a database