Closed BrainCrumbz closed 7 years ago
As a source, we could consider DotNetTestSample readme. As well as examples from other runner, [dotnet-test-nunit](like https://github.com/nunit/dotnet-test-nunit)
Suggestion: when mentioning NSpecRunner in Getting started chapter, we could mention something like: "to run tests in other scenarios like Visual Studio Test Explorer and .NET Core Command Line Interface, have a look at Runners section".
Then have a Runners section at bottom of page with related info.
Comments moved to #164 . Closing this
@amirrajan currently the getting started section is centered around a .NET Framework experience.
Needed settings are different in .NET Core projects. Also, the way to run tests is different as well: there's dotnet test (and in the future there will be VS integration, without need for another adapter).
Q1: Where should we put the .NET Core getting started? Q2: Should we mention that current getting started is for .NET Framework?