I’m a big fan of SpecFlow, a BDD style testing framework for .NET. For me it was a life changer, that made testing fun again.
As you start to use SpecFlow more and more, you’ll see the same test steps appear over and over again. The guys from Endjin recognized the same pattern and bundled some of these steps in a re-usable NuGet package(together with some other useful functionality) .
Here is the list of features from the GitHub site:
Remark: Also check the other SpecFlow extensions they made; Endjin.SpecFlow.Composition and Endjin.SpecFlow.Owin.Hosting
As you start to use SpecFlow more and more, you’ll see the same test steps appear over and over again. The guys from Endjin recognized the same pattern and bundled some of these steps in a re-usable NuGet package(together with some other useful functionality) .
Here is the list of features from the GitHub site:
- Path & ScenarioContext extensions
- Shared Steps for dealing with Exceptions:
And Results:[Then(@"an ""(.*)"" should be thrown")] [Then(@"a ""(.*)"" should be thrown")]
[Then(@"the result count should be (.*)")] [Then(@"the result should equal the datetime (.*)")] [Then(@"the result should equal the datetimeoffset (.*)")] [Then(@"the result should equal the integer (.*)")] [Then(@"the result should equal the string ""(.*)""")] [Then(@"the result should be false")] [Then(@"the result should be greater than the datetime (.*)")] [Then(@"the result should be greater than the datetimeoffset (.*)")] [Then(@"the result should be greater than the integer (.*)")] [Then(@"the result should be greater than or equal to the datetime (.*)")] [Then(@"the result should be greater than or equal to the datetimeoffset (.*)")] [Then(@"the result should be greater than or equal to the integer (.*)")] [Then(@"the result should be less than the datetime (.*)")] [Then(@"the result should be less than the datetimeoffset (.*)")] [Then(@"the result should be less than the integer (.*)")] [Then(@"the result should be less than or equal to the datetime (.*)")] [Then(@"the result should be less than or equal to the datetimeoffset (.*)")] [Then(@"the result should be less than or equal to the integer (.*)")] [Then(@"the result should be null")] [Then(@"the result should be of type (.*)")] [Then(@"the result should be true")] [Then(@"the result should contain")] [Then(@"the result should equal the context value (.*)")] [Then(@"the result should not be null")] [Then(@"the result should not equal the string ""(.*)""")]
- Custom step argument transformations:
- TimeSpan transformation converts to TimeSpan for the following free-text argument formats:
1 day, 1 hour, 1 minute, 1 second 5 days, 4 hours, 3 minutes, 2 seconds 5 days, 4 hours, 3 minutes 5 days, 3 minutes, 2 seconds 5 days, 4 hours, 2 seconds 4 hours, 3 minutes, 2 seconds 5 days, 4 hours 5 days, 3 minutes 5 days, 2 seconds 4 hours, 3 minutes 4 hours, 2 seconds 3 minutes, 2 seconds 5 days 4 hours 3 minutes 2 seconds
- TimeSpan transformation converts to TimeSpan for the following free-text argument formats:
Remark: Also check the other SpecFlow extensions they made; Endjin.SpecFlow.Composition and Endjin.SpecFlow.Owin.Hosting