Releases: getgauge/gauge
Releases · getgauge/gauge
gauge 0.8.3
Enhancements
- Set up gauge config directory if not present on running any
gaugecommand
gauge 0.8.2
Notes
With this relaese Gauge installs it's configration at user level. This helps Gauge to install plugins without elevated paermission.
Enhancements
- #544 - Use
GAUGE_ROOTto customize the location of gauge configs and plugins - #487 - gauge_clear_state_level = scenario should be a property in default.properties
Bug Fixes
- #589 - Getting an error while installing Gauge on Windows
- #572 - After installing gauge 0.8.0 windows installer system PATH variable contains only C:\Program Files\Gauge\bin
- #556 - Mac zip installer fails
- #500 - Doesn't install plugins if gauge is installed at custom location.
- #587 - windows installer: allow silent install to take plugins as arguments
- #577 - Improve Gauge installation
- #576 - Include options to install plugins via installer - linux
- #575 - Include options to install plugins via installer - osx pkg
- #574 - Include options to install plugins via installer - Windows
- #567 - Version check and platform check
- #564 - Difference in behavior when plugin is not installed
gauge 0.8.1
gauge 0.8.0
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
gauge 0.7.0
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
gauge 0.6.2
gauge 0.6.1
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/"
gauge 0.6.0
New Features
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
FailedItemsis empty in .gauge/failed.json
Contributors
A big thanks to @maquessime for contributing to this release!
Gauge 0.5.0
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
Gauge 0.4.0
New Features
Enhancements
- #292 - Versions in
gauge -vshould 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