gauge
gauge copied to clipboard
getgauge
Light weight cross-platform test automation
* [ ] dotnet * [ ] java * [ ] js * [ ] python * [ ] ruby
Gauge LSP server should support formatting concepts files. When an LSP client asks gauge to format a concept file, gauge should format the concept. This story is part of [LSP...
It will be useful to have a Setup steps (context) and TearDown steps which will run before and after spec (instead of before and after each scenario) - similar to...
### Expected behavior The behavior should be same for IDE and command line ### Actual behavior Steps implemented in Kotlin instead of java works fine from IntelliJ but from command...
### Expected behavior Screenshot should get captured irrespective of spaces in folder structure, when there is a failure in spec with `screenshot_on_failure` set to `true` in `default.properties` Example: `C:\User\sample project\...
Gauge error messages should be printed in proper format. However when runner is not installed or fails to install during execution, the error message is not formatted. Ex: when runner...
### Expected behavior `gauge run specs` should exit with a non-zero code when there are failures at the hooks level. These failures should be considered as test failures and should...
### Expected behavior gauge format formats concept and spec files alike. ### Actual behavior Concept file not formatted. ### Steps to reproduce 1. Create spec file with unformatted table ```...
This is the json report for my execution. [result.zip](https://github.com/getgauge-contrib/json-report/files/3137370/result.zip) At the end of the file, it shows; ` "beforeSuiteHookFailure": null, "afterSuiteHookFailure": null, "passedSpecsCount": 14, "failedSpecsCount": 1, "skippedSpecsCount": 0, "passedScenariosCount": 45,...
We start apiService and provide a connection to the runners using the env variable `GAUGE_API_PORT`. This is used only by a few runners to fetch stepValue for a given step...