Improvements:
- Support for SpecFlow v3.8, v3.9 projects (Issue #72)
- Do not log discovery output (Issue #71)
- Support for projects referencing ASP.NET Core 3.1 framework elements
- Support for Gherkin v20 (tagged rules, rules with background -- SpecFlow does not support these yet)
Improvements:
- Support for .NET 5 projects (Issue #67, thx for Timothée Lecomte)
- Support for SpecFlow v3.7 projects (Issue #69)
- Do not warn for missing 'SpecFlow.Tools.MsBuild.Generation' package when SpecFlow v3.3 or later is used
Improvements:
- Extend Cucumber expressions support for SpecFlow v3.3 using CucumberExpressions.SpecFlow.3-3 NuGet package
Improvements:
- Support for Cucumber expressions by using the CucumberExpressions.SpecFlow.3-1 NuGet package (Issue #65)
- Imroved error handling of binding errors (e.g. invalid regular expression)
- Suggested suffix for step definition classes changed to
StepDefinitions(fromSteps) - Detect platform target (x86, x64) automatically (Issue #50)
Improvements:
- Setting
processorArchitecturein config file will determined which dotnet.exe version to use. (Issue #62)
Improvements:
- Support for .NET Core 3.1 projects (Issue #57)
Bug fixes:
- Define steps command overwrites existing step definition files (Issue #51)
New features:
- Support for Gherkin v6
Rulekeyword (with SpecFlow v3.1)
Improvements:
- Add support for feature and scenario scoping
Bug fixes:
- Discovery error when
specflow.jsonis used for .NET Framework project (Issue #56)
Bug fixes:
- Initialisation error with .NET Core and SpecFlow v3.1 beta (Issue #49)
Bug fixes:
- Visual Studio freezes and restart when adding a new feature file to an SDK-style project (Issue #46)
Bug fixes:
- Getting type initializer exception for 'Equ.MemberwiseEquatable'1' when creating feature file for Specflow (Issue #45)
New features:
- Provide documentation in autocompletion of keywords (Issue #3)
- Support projects with SpecFlow assembly references (non-NuGet). See http://speclink.me/deveroomsfassref for details. (Issue #14)
- Deveroom configuration file support. See http://speclink.me/deveroomconfig for details.
- Allow opening artifacts related to scenarios in browser, based on configured tags that match to a specific pattern (automatically recognizes SpecSync for Azure DevOps tags and configurable for others). See http://speclink.me/deveroomtraceability for details.
Improvements:
- Step completion should use word containment for filtering the list (Issue #28)
- Display warning on config load error
- Improved error handling for code-behind generation
Bug fixes:
- Editor: No syntax coloring when the file ends with doc-string open (Issue #6)
- Default language is not detected for SpecFlow v3 from specflow.json config file
This is the first open-source release from GitHub: https://github.com/specsolutions/deveroom-visualstudio
New features:
- Higlight DataTable headers (Issue #31)
Bug fixes:
- Unable to discover step definitions for SpecFlow v3.0.220 (Issue #38)
- Table autoformat removes unfinished cells at the end (Issue #40)
- Editor should tolerate backslash at the end of the line in a DataTable (Issue #39)
- Regenerate Feature.cs file comes back as error if there is a space in the project path (Issue #34)
- Deveroom might call BeforeTestRun event during binding discovery with SpecFlow v3 on .NET Framework (Issue #27)
See more information at: http://gasparnagy.com/2019/04/deveroom-goes-open-source/
There are a few preparation steps ahead but they will not take more than a few weeks. Stay tuned on our GitHub project and our twitter channel (@SpecSol_BDD) to get the latest updates.
Important changes:
- The "deveroom-feedback" project, where we have collected the Deveroom issues has been renamed to https://github.com/specsolutions/deveroom-visualstudio, with all the existing issues. Please use the new link (https://github.com/specsolutions/deveroom-visualstudio/issues) for providing feedback from now on!
Bug fixes:
- Deveroom might call BeforeTestRun event during binding discovery (Issue #27)
New features:
- Find Step Definition Usages (Ctrl B,F) - Can be invoked from the context menu of a binding class. Supports finding usages of a step definition of a shared step definition project; allows showing the results in the output window as well.
- Collapsable outlining for feature files
- Regenerate All Feature File Code-behind command (on the context menu of the project)
- Filter auto-completion list according to entered phrase (Issue #16)
Bug fixes:
- Deveroom fails to discover step definitions when App.config does not contain a node (Issue #24)
- Error while building the project - Unable to copy file "obj\Debug..." to "bin\Debug..." (Issue #26)
- Dialogs are not in the center of the screen (Issue #17)
- No info links provided in the VS extension details (Issue #18)
- Improve error diagnostics
Bug fixes:
- Unable to jump to async step definitions (Issue #23)
Bug fixes:
- "Add new feature file" causes assembly load error (Issue #20, reminder for myself: never do last minute changes after regression testing)
New features:
- Visual Studio 2019 support (tested with VS2019 RC3)
Bug fixes:
- Improve error diagnostics
New features:
- Welcome and What's new screen
Bug fixes:
- Improve error diagnostics
- Improve .NET Core binding discovery
- .NET Core Bindings: Bindings not discovered on slow machines (Issue #11)
- .NET Core Bindings: Project dependency load issue (Issue #5)
Bug fixes:
- Ask user to upgrade Visual Studio or report error on initialization errors (Issue #9)
- Deveroom init: FileNotFoundException: Could not load file or assembly System.Net.Http (Issue #8)
- Improve error diagnostics
- Escaping regex character \ is displayed when using auto completion in a .feature file. (Issue #2)
- Binding: Error: CreatePersistentTrackingPosition: Exception: System.ArgumentException: Must be non-negative. (Issue #10)
Bug fixes:
- CreatePersistentTrackingPosition Exception / Step navigation error
- .NET Core Bindings: Unable to load BoDi.dll (temporary fix)
- Initial release