#1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration
It was in namespace TechTalk.SpecFlow.Infrastructure that is an internal namespace and not suppose to be needed for regular end users. Technically it is a breaking change, but users of ISpecFlowOutputHelper surely had the TechTalk.SpecFlow namespace, e.g. for the [Given/When/Then] attributes.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] Performance improvement
[ ] Refactoring (so no functional change)
[ ] Other (docs, build config, etc)
Checklist:
[ ] I've added tests for my code. (most of the time mandatory)
[x] I have added an entry to the changelog. (mandatory)
[ ] My change requires a change to the documentation.
It was in namespace
TechTalk.SpecFlow.Infrastructurethat is an internal namespace and not suppose to be needed for regular end users. Technically it is a breaking change, but users ofISpecFlowOutputHelpersurely had theTechTalk.SpecFlownamespace, e.g. for the[Given/When/Then]attributes.Types of changes
Checklist: