getgauge-contrib/json-report issues and pull requests

#28 - Bump google.golang.org/grpc from 1.25.1 to 1.53.0

Pull Request - State: open - Opened by dependabot[bot] over 1 year ago
Labels: dependencies

#27 - "result:"{} sections shouldn't contain "screenshot": and "stacktrace": since they are verbose

Issue - State: open - Opened by cemerick1 over 1 year ago

#26 - Alpine: Error starting plugin JSON Report 0.3.7. fork/exec bin/json-report: no such file or directory

Issue - State: closed - Opened by rodafr over 1 year ago - 2 comments

#25 - export json report types to allow unmarshaling

Issue - State: open - Opened by odedpriva about 2 years ago

#24 - setup deploy workflow go version

Pull Request - State: closed - Opened by BrudiBanani about 2 years ago - 1 comment

#23 - Add arm64 support

Pull Request - State: closed - Opened by BrudiBanani about 2 years ago - 2 comments

#22 - Failing to update plugin

Issue - State: closed - Opened by adalberto02 over 3 years ago - 5 comments

#21 - Add before and after scenario and step hook messages

Pull Request - State: closed - Opened by henriheimann over 3 years ago - 7 comments

#20 - json report screenshot missing fix

Pull Request - State: closed - Opened by dibyaranjan-pg over 4 years ago

#19 - failure screenshot is missing in json report

Issue - State: closed - Opened by dibyaranjan-pg over 4 years ago - 6 comments

#18 - ProtoScenario.preHookMessages not visible in Json-Report

Issue - State: closed - Opened by r-vanooyen over 4 years ago - 3 comments

#17 - As in HTML report, please add retryCount in JSON report

Issue - State: open - Opened by dibyaranjan-pg over 4 years ago

#16 - [Feature] Ability to add user data to the report

Issue - State: open - Opened by alpha1592 over 4 years ago

#15 - Scenario Heading is the same for each row of a CSV or Table execution

Issue - State: open - Opened by alpha1592 over 4 years ago

#14 - Json plugin reports are not consistently same

Issue - State: open - Opened by manavghaigithub almost 5 years ago - 4 comments

#13 - Use gRPC to communicate with gauge

Pull Request - State: closed - Opened by shubhamsc almost 5 years ago

#12 - Release json-report 0.3.2

Issue - State: closed - Opened by nehashri about 5 years ago

#11 - Updating json report

Pull Request - State: closed - Opened by nehashri about 5 years ago

#10 - 0.3.1 doesn't ship the right binary for linux

Issue - State: closed - Opened by rbelouin over 5 years ago - 1 comment

#9 - "failedScenariosCount" is invalid in the json-report

Issue - State: closed - Opened by osandadeshan over 5 years ago - 3 comments

#8 - Execution status changed to the past tense

Pull Request - State: closed - Opened by osandadeshan over 5 years ago

#7 - Execution status should be in past tense

Issue - State: closed - Opened by osandadeshan over 5 years ago - 6 comments
Labels: enhancement

#6 - Link does not allow us to download in our company the JSON Report Plugin

Issue - State: closed - Opened by harimadusumilli over 5 years ago - 5 comments

#5 - Concept arguments not showing up in step text.

Issue - State: closed - Opened by ConfusedSky almost 6 years ago - 6 comments
Labels: enhancement

#4 - Gauge JSON report link in gauge plugins page points to wrong location

Issue - State: closed - Opened by arun2sasi about 6 years ago - 2 comments

#3 - There should be the total number of passed/failed/skipped scenario counts in the json-report

Issue - State: closed - Opened by osandadeshan over 6 years ago - 3 comments

#2 - Update readme

Pull Request - State: closed - Opened by BugDiver over 6 years ago

#1 - Context array details are overwritten by teardown data

Issue - State: closed - Opened by sushilveer over 7 years ago - 1 comment
Labels: bug

Ecosyste.ms: Issues

GitHub / getgauge-contrib/json-report issues and pull requests