Closed david1995 closed 5 years ago
In addition to the aforementioned project templates, these item templates should be created too:
default.srprofile
: template name specflow-plus-profile
specflow-feature
specflow.json
: template name specflow-json
I'd like to do that
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
This is basically the same as #1575, but is intended for
dotnet new
tooling support instead of Visual Studio.At the moment, creating a SpecFlow project is more complicated than it could be. You have to create a class library or unit test project in Visual Studio, and add required SpecFlow packages manually to the project.
To improve UX for creating SpecFlow projects without Visual Studio, the following SpecFlow project templates should be created for use with
dotnet new
:All project templates should follow these principles:
.feature
files are to be placed in a subfolderFeatures
Steps
Drivers
subfolder is to be createdHooks
subfolder is to be createdSpecFlow.Tools.MsBuild.Generation
packageSpecFlowSingleFileGenerator
must not be set as Custom Tool on any.feature
file.gitignore
file to the project root folder which excludes.feature.cs
filesapp.config
,specflow.json
ordefault.srprofile
files are to be added by defaultIn summary, these are the packages that should be referenced in the templates:
SpecFlow
SpecFlow.Tools.MsBuild.Generation
SpecFlow.XUnit
,SpecFlow.NUnit
,SpecFlow.MsTest
orSpecRun.SpecFlow-3-0-0
, depending on unit test providerMicrosoft.NET.Test.Sdk
, version 15.0.0xUnit.Runner.VisualStudio
for xUnit