Skip to content
This repository was archived by the owner on Jul 20, 2020. It is now read-only.

Gauge Visual Studio Plugin 0.3.0
Compare
Choose a tag to compare
@gaugeci gaugeci released this 17 Feb 06:50
· 108 commits to master since this release
v0.3.0
8ddaadb

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.

Assets 3
Loading