Skip to main content

Comments

4 comments

  • Jacob Maristany

    IMHO, the VS4M support should be similar to Visual Studio 2019 support and at least cover these useful features: All of this is also missing from the Straight8 Specflow extension for VS4M. 

    1) Allow *.feature files to show in the Solution pad (they currently will not). 
    2) Syntax highlighting for feature files
    3) Consistent feature class (feature.cs) file generation with the Visual Studio 2019 extension (so builds from different machines do not produce different results). 
    4) "Go to step definition" context support in feature files. 
    5) "Generate step definitions" context support for feature files. 

    2
  • Andreas Willich

    About 3) Consistent feature class (feature.cs) file generation with the Visual Studio 2019 extension (so builds from different machines do not produce different results). 

     

    If you are using the SpecFlow.Tools.MSBuild.Generation NuGet package in your project, the output should be the same on Windows and Linux. All is done in MSBuild during compile time. If it isn't, please open an issue on GitHub with details what is different.

    0
  • Jacob Maristany

    It is different. I'll open an issue. The difference is that on macOS, the tooling TestName into the DescriptionAttribute and and leaves the TextFixtureAttribute blank. 

    0

Please sign in to leave a comment.

Powered by Zendesk