Releases: getgauge-contrib/json-report
Releases · getgauge-contrib/json-report
JSON Report v0.4.0
JSON Report v0.3.7
What's Changed
- Add arm64 support by @BrudiBanani in #23
- setup deploy workflow go version by @BrudiBanani in #24
New Contributors
- @BrudiBanani made their first contribution in #23
Full Changelog: v0.3.6...v0.3.7
JSON Report v0.3.6
Enhancements
- ProtoScenario.preHookMessages not visible in Json-Report (#18 ) - thanks @henriheimann
JSON Report v0.3.5
JSON Report v0.3.3
Enhancements
- Use gRPC for communicating with gauge getgauge/gauge#134
Bug Fixes
- #10 - 0.3.1 doesn't ship the right binary for linux
json-report v0.3.2
Bug Fixes
- fixes spec hook failure conversion
Miscellaneous
- #7 Execution status should be in the past tense
- removed vendor
- updated proto messages
Thanks, @osandadeshan for contributing to this release!
JSON Report v0.3.1
Enhancements
- Execution status in past tense - #7. Thanks to @osandadeshan
Changelog Description
The field executionStatus
in various levels of JSON report, like suite, scenario will now have status in past tense. i.e pass
-> passed
, fail
-> failed
, skip
-> skipped
.
Gauge JSON report v0.3.0
Enhancements
- Include step parameters as a new field in json under step/concept. #5
The new fieldParameters
in step includes all the various types of parameters with their values, including static parameters, dynamic, table and special params.
Example:
"parameters": [
{
"parameterType": "dynamic",
"name": "word",
"value": "gauge",
"table": null
},
{
"parameterType": "static",
"name": "",
"value": "3",
"table": null
}],
Updated complete JSON Schema can be found here: https://apoorvam.github.io/json-report/
Note: Table
field in Step is now deprecated since its included in Parameters and will be removed in next release.
Gauge JSON Report v0.2.2
Enhancements
- Include
passedScenariosCount
,failedScenariosCount
,skippedScenariosCount
in suite result - #3
JSON Report v0.2.1
Bug fixes
- Context step results being over-written by teardown results in scenario #1