This repository was archived by the owner on Jul 20, 2020. It is now read-only.
Releases: getgauge/gauge-visualstudio
Releases · getgauge/gauge-visualstudio
gauge-visualstudio 0.3.8
gauge-visualstudio 0.3.7
Bug Fixes
- #246 - Unable to debug tests in VS 2017
gauge-visualstudio 0.3.6
gauge-visualstudio 0.3.5
Enhancements
Bug Fixes
- #198 - Unable to debug spec from visual studio 2015
- #217 - Test explorer should display all the specs for execution
- #223 - Significant lag in Visual Studio on larger Gauge project
- #225 - Lag in VisualStudio on editing step lines within a spec.
- #229 - Should be able to run specifications after project creation
gauge-visualstudio
Enhancements
- #210 - Use Gauge's JSON output for test runner
- #170 - Stop build on Document Save
- #113 - Mark Scenarios with missing Step implementations as "Inconclusive"
Bug Fixes
- #220 - Failed to start gauge api
- #219 - Unable to refactor concept
- #216 - Unable to create Gauge project from IDE
- #214 - Debugging scenarios doesn't hit breakpoints
- #213 - Multiple step implementations found. Gauge will skip execution of this scenario
- #206 - Saving files is slow with the Gauge VS plugin
- #205 - ImplementStep doesn't work in VS2015 Community
- #184 - On successful installation the document page opening is giving 404
- #180 - When rebuilding solution with compile errors the gauge Extension causes VS2015 to crash
- #175 - Opening a visual studio project with only Gauge core installed is giving exception
- #166 - Steps with implementation shown as unimplemented
- #159 - The skipped scenarios are also marked as passed
- #151 - [Performance] The process of discovering the tests after the execution of tests take too long
- #134 - The actions save take a lot of time
- #125 - A newly created concept is not available in auto-complete
- #120 - Running the test multiple times
- #72 - report doesn't show all results when execute all specs from IDE
- #70 - Executing single test case multiple times and displays multiple output for same in IDE
Miscellaneous
- #218 - included ProjectTemplates and ItemTemplates in solution and in vsixmanifest
- #215 - Project and Spec file templates don't appear in VS project templates
- #212 - Scenarios execution with unimplemented steps is not finishing
- #211 - Test reporter improvements
- #209 - performance improvements, #134 #151 #170 #206
- #204 - Random issues with Visual Studio 2015 Plugin
- #202 - Gauge Visual studio plugin executing scenario in alphabetically instead of scenario sequence.
- #198 - Unable to debug spec from visual studio 2015
- #195 - Versioning Issue
gauge-visualstudio
Enhancements
- #208 - use native visual studio format command
Bug Fixes
- #203 - Getting a deprecated message on IDE
- #193 - Concept file does not have syntax highlighting
- #150 - Getting an exception DllNotFound
- #200 - Gauge-Error Occurred Unable to launch Gauge Daemon.
- #199 - cant install gauge plugin for visual studio 2013 and 2015
- #196 - Unable to debug spec from visual studio 2015
- #183 - Make Gauge Daemon stop running for every project within solution
- #176 - VS2015 Enterprise unable to open plugin after installation
Note: This version will only work with Gauge v0.9.4 or later
gauge-visualstudio
Bug Fixes
- #195- Versioning Issue
Gauge Visual Studio Plugin 0.3.0
New Features
- #105 - Debugging support for VS 2015
Enhancements
- #104 - Autocomplete : scan for unused steps
Bug Fixes
- #162 - Use warning icons while displaying warnings
- #161 - Getting an exception while opening a spec file
- #155 - Find usage should match for the given step only
- #145 - protected step implementations are not available for execution, however one is taken to it on goto definition
- #126 - Test explorer does not refresh when a spec file is deleted
- #119 - Test execution doesn't work with space in the directory path
- #118 - If there is a step with multiple implementations not able to navigate to the step
- #117 - Does not highlight steps implemented in a different project
- #110 - Unable to refactor a step to have special characters
- #109 - On refactoring, the spec file content changes to the last saved version
- #108 - Does not show the parse error that fails the refactor step
Deprecation Notice
Gauge-VisualStudio plugin's support for Visual Studio 2013 will end on 30th June 2017. If you are using Visual Studio 2013 with Gauge then we recommend that you consider upgrading to Visual Studio 2015 for all the support and bug fixes.
However if you are tied to Visual Studion 2013 for some reason, you will still be able to download and install the plugin, but there will be no upgrades/support to it.
In the meantime, we will work towards releasing support for Gauge with Visual Studio 2017, which is currently in RC.
Why are we doing this?
Over the years Visual Studio has evolved and so has it's SDK and extension points. We believe that some of the features available in VS 2015 and above will benefit Gauge users. Also, later version of Visual Studio SDK packages have been published and not all of these work with Visual Studio 2013. We believe that dropping support for Visual Studio 2013 will enable us to embrace the newer extension points and provide better support for authoring specs.
Gauge Visual Studio Plugin 0.2.3
Enhancements
- #148 - Check for Gauge and Gauge C# installation
Bug Fixes
- #156 - Should be able to open spec files without getting an exception
- #154 - Unable to continue working on an old project with latest VS nightly
- #153 - Should be able to run a project created from web driver template
- #149 - Getting an exception with Gauge nightly
- #147 - VS Exception - gauge TextSnapshotExtensions, something to do with UnimplementedStepTagger
- #141 - How to stop an existing running test in Visual studio
- #152 - [Refactor] Unable to refactor from the IDE
- #137 - VS Extension is not compatible to latest gauge csharp plugin
