Enhancements

• getgauge/gauge-proto#3 Migrated from Proto2 to Proto3.
• #389 - Additional details on console while running via command line using tags

Bug Fixes

• #565 - Installing Gauge on windows is not installing html-report along with it
• #562 - Uninstall exe not found
• #551 - Create step implementation considers table as parameter even when it should not
• #550 - Should get parse error Table doesn’t belong to any step
• #535 - panic: Accessing an invalid parameter
• #408 - Data driven execution --table-rows executes specs even if out of range
• #256 - Make the csv table file respect whitespace if columns are quoted
• #543 - Gauge uses PluginConnection timeout instead of KillConnectionTimeout
• #533 - Have a structured format for the errors
• #528 - Steps with enum parameter marked as continueOnFailure is not working as expected

New Features

• #491 - Portable Gauge installer for Windows
• #501 - Plain binary download
• #495 - To run specific table rows during Data driven execution

Enhancements

• #393 - gauge.writeMessage in hooks is not printing any message
• #363 - Pass on executed table row info to reports
• #477 - gauge --format --verbose does not give any information
• #412 - Overwriting manifest.json, default.properties while creating the gauge --init

Bug Fixes

• #530 - [Table Driven Exec] Spec is not executed against the first blank table row if header underline is not present
• #524 - Underlines in table header in concepts is being considered as a table row
• #521 - Execute teardown steps whenever the context steps are executed
• #520 - Getting exception on executing some basic specs
• #517 - Spelling of "Step implementation" is "Step implemenatation"
• #516 - With Compilation error in code, Gauge exits after timing out
• #485 - Spec with tab is not getting formatted as expected
• #387 - wrong table rows getting executed
• #526 - Unable to create new project using init - "Failed to find project directory issue"
• #515 - Formatting adds a space at end of line

Enhancements

• #509 - Handle utf-8 files with signature

Bug Fixes

• #505 - Teardown Steps should be executed irrespective of failure in Context Steps.

Bug Fixes

• #488 - Statistics generated of a skipped scenario with continue on failure is wrong
• #484 - Continue on failure not working for context steps
• #457 - Gauge process is getting killed, when specs folder is executed along with a child spec with unimplemented step

Miscellaneous

• #486 - Link is broken for installing guage "http://getgauge.io/documentation/user/current/installations/"

New Features

• #290 - Export specs to HTML
• #255 - Continue on failure of recoverable steps

Enhancements

• #467 - Show error on duplicate step implementation
• #440 - Add support to execute scenario by line number

Bug Fixes

• #475 - Content comes from skel folder even if a template exists
• #466 - Gauge process getting killed when editing a concept
• #464 - running gauge --docs m2h is giving an exception
• #460 - Validation error displays line number of a concept and name of a spec
• #459 - Parse errors of a concept is not getting listed when the consolidated errors is displayed
• #448 - Could not resolve table from table giving wrong line number
• #444 - Scenario with no steps is getting executed and shown as passed
• #427 - Concept with static parameter is not giving a parse error
• #418 - "gauge --failed" runs all specs from "specs/" subdirectory when FailedItems is empty in .gauge/failed.json

Contributors

A big thanks to @maquessime for contributing to this release!

New Features

• #105 - Add ability to run failed scenarios from previous run

Enhancements

• #413 - Warn if reporting-plugin is mentioned in manifest but not installed
• #382 - Concepts not resolved when a spec is executed
• #353 - Refactoring of Tear down steps
• #349 - Should show all parse errors together instead of one by one
• Add support to execute scenario by line number
• #298 - Add spec file name and step line number in case of failure

Bug Fixes

• #438 - gauge --validate should take specs directory as default
• #437 - Step implementation not found message incomplete
• #436 - Parse error is not showing a file name
• #434 - Saving a spec with table header blank is throwing an exception and killing gauge
• #428 - getting an exception for a table with no header
• #422 - Duplicate concept definition does not indicate the file name
• #410 - With multiple tags for a scenario the previous tags are being overwritten
• #407 - should be able to use the file separator specific to the OS to run command line
• #402 - Does not give the duplicate definition of the concept when 2 files have same multiple concept definitions
• #439 - Showing negative numbers in execution summary
• #405 - GetAllSpecsRequest is returning invalid response when Teardown steps are present
• #397 - Tries to create project for an invalid language runner
• #385 - Uninstalling multiple versions even when specific version given

New Features

• #243 - Install plugins globally
• #197 - Check for product updates

Enhancements

• #292 - Versions in gauge -v should reflect nightly builds
• #244 - Provide a consistent way to find plugin version
• #194 - Hook for plugin uninstall
• #100 - Add Notice file to all distributable

Bug Fixes

• #309 - screenshot_on_failure = false is ignored on 0.3.2
• #303 - Invalid execution summary when no scenarios are run
• #302 - Gauge uses hardcoded specs folder (at least in the logs)
• #295 - Gauge not installing plugin while doing --init, if plugin is not installed
• #294 - Gauge not installing plugins
• #166 - Get rid of orphan gauge processes

New Features:

• #282 - Pass environment variables and command line arguments to the runner.
• #240 - Added support for teardown section in a specification.

Enhancements:

• Adding progress indicator while installing plugins.
• #110 - Added support for Internet Proxy Settings.
• #296 - Take a backup of gauge.properties file if the contents of file are changed while installing Gauge.

Bug Fixes:

• #60 - Skipping specification with no scenarios while execution.
• #166 - Get rid of orphan gauge processes(fixed for Linux, Mac).

Bug Fixes:

• Windows installer overwrites the PATH if its more than 1024 chars #150

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 --verbose flag. 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.2 or gauge --update java --plugin-version=0.3.2. Thanks @Thunderforge for the suggestion.
• The --check flag has been deprecated. It will be removed in the next version. You can use the --validate flag 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

• @Thunderforge
• @tanob
• @bentatham
• @gprestes
• @ben-biddington
• @manupsunny

Bug fixes:

• #234 - Showing Pre and Post hook failure error messages on the console.
• #232 - Fixed Failed to start runner error in case of Parallel Execution

New Features:

• #217 - Lazy parallelization strategy for spec execution
• #213 - Adding --check flag 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-all flag to update all the plugins installed using Gauge.

Bug Fixes:

• #104 - Clearing gauge_temp after install and update of plugin
• #211 - Handling case where escape char is present in dynamic param value
• #227 - Printing gauge usage irrespective of the current dir

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.

Bug fixes:

• #183 Step panics if table from csv is empty
• #186 Adding colon in step description fails
• #187 Increase connection timeouts
• #207 Gauge does not honors absolute path in special params in Windows

Enhancements:

• Show all parse errors on parse failure

Bug fixes:

• Error Messages updated #169
• Console log in Windows #73
• Params in nested concepts #181

Enhancements:

• Generating pkgs for Mac OS X instead of zips

Bug fixes:

• #173 Execution fails for nested concepts
• #174 HTML report generation fails when a external table is used in the spec file

Enhancements:

• Adding API message for formatting spec files - #164

Bug fixes:

• Handling static arguments in nested concept usage - #157

Enhancements

• No repeated runners invokes during execution - #34

Bug fixes

• Runner compatibility check at project init - #142
• Error thrown due to spec directory deletion - #144

New Features:

• Install all plugins in manifest file using --install-all #139

Enhancements:

• Optimized Gauge API - #120

Bug fixes:

• #124
• #135
• #91
• #136

• Fixing incorrect version number

Enhancements:

• Unresolved dynamic params are treated as static params.
• Environment variable runner_request_timeout overrides timeout from gauge.properties file.

Changes:

• Changing runner_request_timeout to10 seconds by default.