Repository files navigation

As at the time of writing (September 2016), theSpecFlow for Visual Studio 2015 extension does not play well with .NET Core projects.

Wait for the VS extension to support .NET Core projects. In the meantime, I present...

Update your project:

1. Include SpecFlow and your test framework of choice:

   • xUnit:

     <ItemGroup>  <PackageReferenceInclude="Microsoft.NET.Test.Sdk"Version="15.3.0" />  <PackageReferenceInclude="SpecFlow"Version="2.1.0" />  <PackageReferenceInclude="xunit.runner.visualstudio"Version="2.2.0" />  <PackageReferenceInclude="xunit"Version="2.2.0" /></ItemGroup>

   • NUnit(Experimental):

     <ItemGroup>  <PackageReferenceInclude="Microsoft.NET.Test.Sdk"Version="15.3.0" />  <PackageReferenceInclude="SpecFlow"Version="2.1.0" />  <PackageReferenceInclude="NUnit"Version="3.8.1" />  <PackageReferenceInclude="dotnet-test-nunit"Version="3.4.0-beta-2" /></ItemGroup>

   • MsTest(Experimental):

     <ItemGroup>  <PackageReferenceInclude="Microsoft.NET.Test.Sdk"Version="15.3.0" />  <PackageReferenceInclude="SpecFlow"Version="2.1.0" />  <PackageReferenceInclude="MSTest.TestAdapter"Version="1.1.18" />  <PackageReferenceInclude="MSTest.TestFramework"Version="1.1.18" /></ItemGroup>

2. IncludeSpecFlow.NetCore:

   <ItemGroup>  <DotNetCliToolReferenceInclude="SpecFlow.NetCore"Version="1.3.5" /></ItemGroup>

3. Add a precompile script:

   <TargetName="PrecompileScript"BeforeTargets="BeforeBuild">  <ExecCommand="dotnet SpecFlow.NetCore" /></Target>

4. Build for your tests to be discovered.

   Note: there isa bug with the .NET Core CLI requiring a second build for newly added files to be discovered.

This has been tested on Windows, Ubuntu and macOS (High Sierra). It works in exactly the same way except it doesn’t use DotNetCli because it doesn’t work cross platform. Instead we call dotnet-SpecFlow.NetCore.exe directly from the package, this is why we need an extra PackageReference to SpecFlow.NetCore.

You also need to reference SpecFlow 2.2 or higher due to aMono specific bug in SpecFlow.

<PropertyGroup>      <SpecFlowNetCoreVersion>1.3.2</SpecFlowNetCoreVersion></PropertyGroup>  <ItemGroup>   <PackageReferenceInclude="SpecFlow.NetCore"Version="$(SpecFlowNetCoreVersion)" />      <PackageReferenceInclude="SpecFlow"Version="2.2.0" />   <PackageReferenceInclude="xunit.runner.visualstudio"Version="2.2.0" />   <PackageReferenceInclude="xunit"Version="2.2.0" /></ItemGroup><TargetName="PrecompileScript"BeforeTargets="BeforeBuild">  <ExecCommand="mono $(NuGetPackageRoot)specflow.netcore/$(SpecFlowNetCoreVersion)/lib/$(TargetFramework)/dotnet-SpecFlow.NetCore.exe" /></Target>

SpecFlow itself is currently limited to Windows platforms with full .NET Framework v4.5.1+. This means that two of the most commontarget frameworks are unsupported:

• .NET Standard (unsupported)
• .NET Core Application (unsupported)
• .NET Framework

For.NET Framework, the following Target Framework Monikers (TFMs) are officially supported:

• net46
• net461

TFMs ofnet451 and above should support SpecFlow and this project, but have not been officially tested.

If you build thesamples solution, you should see.feature.cs files and anapp.config being generated for each test framework.

• SpecFlow Issue 471: Auto generation offeature.cs fails when using MSBuild that comes with VS2015
• SpecFlow Issue 457: SpecFlow "Generate Step Definition" context menu missing in VS2015
• SpecFlow Google Group discussing VS2015 & DNX