V2.2.0
Core changes:
- Projects are now read by XML and not with MSBuild. The general functionality is working. If something is missing, please file an issue and look at https://github.com/techtalk/SpecFlow/blob/master/TechTalk.SpecFlow.Generator/Project/MsBuildProjectReader.cs
- Before/After- Feature Hooks can get the FeatureContext by parameter See #779
Fixes:
- Fix in executing the code behind generation #855
- Fix, that hook with multiple tags is executed more than once #848
- Removed obsolete marked StepScopeAttribute - use the ScopeAttribute for it
- Fixed: Projection.Equals() returns false unnecessarily if table headers differ from property name by casing
- Fixed regex-less step definition support, see StepDefinitionsWithoutRegex.feature for details (Issues #715, #301)
- The results of comparisons made against sets will be displayed as a comma-delimited list.
- Fix code generation for VB.Net
- Scenario Outline example tags do now appear in ScenarioContext.ScenarioInfo.Tags
- Fix scenario outline variants showing without source code if generating row tests is disabled
- Fix code behind generation if it is tiggered through Save in Visual Studio (#877)
New Features:
- Order sensitive overload for compare to set #778
- MsTest: Support for [DeploymentItem] attribute with @mstest:DeploymentItem tag (Issue 803)
- Json Configuration support: you can put your SpecFlow configuration into a specflow.json also (#690)
Examples: https://github.com/techtalk/SpecFlow/blob/master/Tests/TechTalk.SpecFlow.RuntimeTests/Configuration/JsonConfigTests.cs - TestThreadContext can be used for test thread related data sharing (#875)
- Support for xUnit2 ITestOutputHelper (#874)
Core changes:
- Upgrade to BoDi 1.3 (#876)
API changes:
- Move SourceFilePath from SpecFlowFeature to SpecFlowDocument