Releases: getgauge/gauge
Releases · getgauge/gauge
gauge 0.3.1
Bug Fixes:
- Windows installer overwrites the PATH if its more than 1024 chars #150
Gauge 0.3.0
What's New
Templates
To make your getting started experience easier, we have added support for templates. You can initialize a project with a particular template and Gauge will create the entire folder structure along with basic build files (if applicable) and the required dependencies.
To begin with, we have added the following templates.
java(Vanilla, without any frameworks, build tools, etc)java_maven(template for creating a Gauge Java project with Maven)java_maven_selenium(template for creating a Gauge Java project with Maven and selenium, includes WebDriverFactory setup)csharp(Vanilla, without any frameworks, build tools, etc)ruby(Vanilla, without any frameworks, build tools, etc)
At any point of time, you can get the list of available templates by running the command gauge --list-templates.
Nightly Builds
We have started publishing nightly builds at https://bintray.com/gauge. They will be published every evening (Monday to Friday) at around 6:00 PM IST.
Plugin Updates
Most of the Gauge plugins have been updated. Click on the respective links to go through the release notes. Please run gauge --update-all to update your plugins.
- Java v0.3.4
- C# v0.7.1
- Ruby v0.1.1
- HTML Report v2.0.0
- XML Report v0.1.2
- IntelliJ v0.1.0
- Maven Plugin v1.1.0
Enhancements
- Console reporting has been enhanced with colored output. For more detailed reports on console, you can use the
--verboseflag. Thanks @navaneeth and @ocary for raising this. - Plugins are now listed in alphabetical order when running
gauge -v. Thanks @Thunderforge for the suggestion. - Lazy parallel execution strategy is now the default strategy. Thanks @Thunderforge for the suggestion.
- Support for uninstalling / updating a specific version of plugin. Example:
gauge --uninstall java --plugin-version=0.3.2orgauge --update java --plugin-version=0.3.2. Thanks @Thunderforge for the suggestion. - The
--checkflag has been deprecated. It will be removed in the next version. You can use the--validateflag instead. The underlying functionality remains the same.
Bug Fixes
- #257 Applying filter on specs with data tables breaks the report
- #267 Gauge.writeMessage in AfterStep hook prints it against next step
- #281 Temporary plugin install dir not deleted
Contributions
Contributors to Gauge core
- @kmugrage - Changed case on GoCD to preferred format in skeleton files
- @haroon-sheikh - More meaningful message when env directory is not found
- @navaneeth - Fixed inconsistent log level
- @carlosmiranda - Fixed test code link in README
- @jean - Fixed the install script for Linux
Contributors to Gauge documentation
Gauge 0.2.1
Gauge 0.2.0
New Features:
- #217 - Lazy parallelization strategy for spec execution
- #213 - Adding
--checkflag for checking parse and validation errors - #224 - updating install script so that user can install gauge as non-root user on linux
- #208 - Skipping scenarios/specifications if validation errors are present.
- Adding
--update-allflag to update all the plugins installed using Gauge.
Bug Fixes:
Gauge 0.1.8
New Features:
- We have added a new flag to uninstall Gauge plugins. You can use it with the name of the plugin you want to uninstall
gauge --uninstall <plugin_name> - You can now comment out lines in csv files by adding
#character at the beginning of the line. - We have signed all the Windows executables.
- Gauge maintains a cache of all the specs, concepts and steps used by the project. We have enhanced the cache refreshing algorithm.
- The log messages have been enhanced.