Open
Conversation
…t framework independent PowerAssert to enable SpecSalad to be used with flavors of SpecFlow like xUnit.Net
Owner
|
Like this idea, need to merge the code locally to tests the effects first with regard to nuget. |
ghost
assigned
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
2 participants
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.
I wanted to use SpecSalad with an xUnit.NET flavor of SpecFlow but the core SpecSalad dependency on NUnit may have prevented that.
It may not have, but in any case when I looked at the SpecSalad source I noticed that there were no dependencies in the core bits beyond using NUnit for Assertions.
In this branch I have removed the core dependence on NUnit and replaced it with the PowerAssert library. This should allow SpecSalad to ride independently on whatever flavor of testing framework that the underlying SpecFlow is configured to generate.