Skip to content

Releases: getgauge/gauge-js

gauge-js 2.3.2

18 Oct 10:05
Compare
Choose a tag to compare

Enhancements

  • #165 - Support async custom screenshot functions

Bug Fixes

  • #150 - Debugging point on a step/hook definition gives timeout
  • #93 - git ignore files should be added to js file templates

Miscellaneous

  • #173 - Add telemetry to measure Gauge and Taiko usage
  • #171 - Pass arguments to node runner
  • #169 - make node runtime and args configurable, #168
  • #166 - Collected step execution screenshots in result of step execution
  • #162 - Allow to capture screenshot in step execution

gauge-js 2.3.1

18 Jun 11:09
Compare
Choose a tag to compare

Enhancements

Bug Fixes

  • #149 - Screenshot is not captured on failure
  • #104 - Refactoring should not cause a script failure

Miscellaneous

  • #146 - File name of the file names generated should be consistent
  • #145 - Deprecated warning on running tests

gauge-js 2.3.0

08 May 09:05
Compare
Choose a tag to compare

Enhancements

  • #132 - Sandbox missing expected globals

Bug Fixes

  • #128 - Should not timeout while debugging
  • #143 - Deleting a file gives connection unavailable
  • #141 - Renaming a file gives grpc connection is unavailable
  • #142 - Custom screenshot not working

Miscellaneous

  • #139 - Information displayed while installing can be minimized
  • #126 - Runner should log to log files when started gauge is started as the daemon

Contributions

  • #133 - Expose standard node.js globals in sandbox

Thanks @mpareja for contributing to this release!

gauge-js 2.2.0

19 Mar 09:16
Compare
Choose a tag to compare

New Features

  • #102 - Debugging support for JS

Enhancements

  • #122 - scanning only dirs specified in STEP_IMPL_DIR env. removed config regex.

Bug Fixes

  • #89 - Current project path is getting appended to external library

Miscellaneous

  • #127 - logging with timestamp if gauge is running as daemon, #126
  • #125 - Adding filename for new file in stub response getgauge/gauge-vscode#155
  • #123 - New Content to come after a blank line, getgauge/gauge-vscode#156
  • #121 - Sending file Diff from runner instead of new content, getgauge/gauge-…
  • #115 - Adding a new line before appending stub implementation code
  • #114 - Runner should not scan the whole project root for files
  • #113 - refactor: split proto load and socket listed into different promises
  • #112 - Skeleton files and templates are out of sync
  • #111 - [Feature Request]: Support regex in step implementation
  • #108 - better refactoring support for paramters. #104
  • #107 - 119 generate stub
  • #106 - Sending aliases with StepNameResponse, #933
  • #100 - Message on goto definition of unimplemented step
  • #99 - Saving changes to file system during refactoring only if explicitly requested.
  • #97 - Stacktrace should contain relative path #96
  • #96 - When run from console, gauge stacktrace should have relative paths

gauge-js 2.1.0

12 Jan 06:35
Compare
Choose a tag to compare

Enhancements

  • #59 - Export step and all the hooks in the global scope
  • #90 - Highlighting the step when showing the peek definition

Bug Fixes

  • #94 - Execution of specs gives Error - Unable to require module
  • #87 - The error path in the stack trace is incomplete
  • #85 - The annotation text of the generated code should have valid parameter details
  • #48 - specify where step implementations are located.

Miscellaneous

  • #82 - Feature/config location

gauge-js 2.0.3

18 Dec 11:23
Compare
Choose a tag to compare

New Features

Enhancements

  • #75 - chopping stacktrace #71
  • #70 - The runner should load source files only for execution
  • #65 - Provide suggestions for unimplemented steps

Bug Fixes

  • #83 - Stacktrace with error in js line should be clickable
  • #77 - Screenshot is not captured even if gauge_screenshot is installed
  • #73 - The line number of failure is one more than the line of error
  • #69 - Refactoring is broken
  • #66 - Refactoring is broken after deprecating gauge.step

Miscellaneous

  • #79 - A javascript file parse results is all steps reported as unimplemented
  • #74 - Adding step span in stepPositionResponse instead of lineNumber
  • #72 - Step registry caches duplicate step file locations
  • #71 - Make failure stack trace cleaner
  • #63 - Provide step position

v2.0.2

25 Oct 06:38
Compare
Choose a tag to compare

New Features

Note: This version will only work with Gauge v0.9.0 and later.

v2.0.1

27 Sep 08:23
0cc0167
Compare
Choose a tag to compare
  • Better support for async/await and promise.
  • Deprecating the following usages.
    • gauge.step() ==> step()
    • gauge.beforeStep() ==> beforeStep()
    • gauge.afterStep() ==> afterStep()
    • gauge.beforeScenario() ==> beforeScenario()
    • gauge.afterScenario() ==> afterScenario()
    • gauge.beforeSpec() ==> beforeSpec()
    • gauge.afterSpec() ==> afterSpec()
    • gauge.beforeSuite() ==> beforeSuite()
    • gauge.afterSuite() ==> afterSuite()

v2.0.0

06 Mar 17:03
Compare
Choose a tag to compare

New feature

  • Adds proto3 support, making it compatible with gauge 0.8.0+ . #52

Note: This version will only work with Gauge v0.8.0 and later.

v1.3.0

06 Jul 10:02
Compare
Choose a tag to compare

New feature

  • Throw validation error on duplicate step implementation. #40

Bug fixes

  • Fix detection of step aliases. #47

Note: This version will only work with Gauge v0.5.1 and later.