Comments (5)
I did and it's working. using it in this way now:
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>netcoreapp2.0</TargetFramework>
<IsPackable>false</IsPackable>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
<LangVersion>latest</LangVersion>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.5.0" />
<PackageReference Include="NUnit" Version="3.9.0" />
<PackageReference Include="NUnit3TestAdapter" Version="3.9.0" />
<PackageReference Include="SpecFlow.NUnit.Runners" Version="2.2.1" />
<PackageReference Include="System.Configuration.ConfigurationManager" Version="4.5.0-preview1-25914-04" />
</ItemGroup>
<ItemGroup>
<DotNetCliToolReference Include="SpecFlow.NetCore" Version="1.0.0" />
</ItemGroup>
<Target Name="PrecompileScript" BeforeTargets="BeforeBuild">
<Exec Command="dotnet SpecFlow.NetCore --specflow-path SpecFlow\2.2.1\tools\specflow.exe" />
</Target>
</Project>
I guess the documentation should be updated.
from specflow.netcore.
Auto-detection of SpecFlow version from the .csproj
was merged yesterday thanks to @oakio (not yet released to nuget.org).
I'll take a PR to improve the README, but at least the output already hints at the solution:
Try specifying the path with --specflow-path.
from specflow.netcore.
You can specify the path yourself as an arg
https://github.com/stajs/SpecFlow.NetCore/blob/master/src/SpecFlow.NetCore/Args.cs#L10
from specflow.netcore.
Agreed, we should update the readme
from specflow.netcore.
https://www.nuget.org/packages/SpecFlow.NetCore/1.1.0
from specflow.netcore.
Related Issues (20)
- dotnet core 2.0 support HOT 5
- Tools version is unsupported HOT 3
- Do not hardcode to SpecFlow 2.1.0 HOT 2
- dotnet SpecFlow.NetCore does not work on linux HOT 6
- Scenarios break when the name is too long HOT 1
- Tools version is unsupported HOT 6
- Build fails when there is an existing fake.csproj file (or any extra csproj file) HOT 4
- .net core 2.0 (CLI) HOT 2
- Error in SpecFlow.NetCore tool during print messages HOT 15
- Consider netcoreapp ONLY compatiblity HOT 2
- Attempt to reduce the confusion of the project name HOT 7
- New NuGet package HOT 2
- Building with Mono doesn't generate files. HOT 3
- Use Project's namespace instead of SpecFlow.GeneratedTests HOT 2
- Project not rebuilding when changing .feature file in VS 2017 (15.7.1) HOT 3
- Different result locally and on CI server HOT 3
- When specifying --specflow-path it doesn't detect SpecFlow Version.
- Version for package 'Specflow.NetCore' could not be resolved HOT 3
- Can you please add support for net core 3 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from specflow.netcore.