Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pass on executed table row info to reports #363

Closed
2 tasks done
mahendrakariya opened this issue Apr 28, 2016 · 1 comment
Closed
2 tasks done

Pass on executed table row info to reports #363

mahendrakariya opened this issue Apr 28, 2016 · 1 comment

Comments

@mahendrakariya
Copy link
Contributor

mahendrakariya commented Apr 28, 2016 •
edited by apoorvam

Reports do not have the information on which table rows are executed, in case --table-rows flag is used by the user. It only has information about the rows that have failed.

As a result, there are a couple of bugs on html-report.

This will require a change in the spec.proto file. The ProtoSpecResult has information only about the failed data table rows and not the ones which have been skipped.
This was referenced Apr 28, 2016
Closed
Closed
sriv added a commit to getgauge/gauge-proto that referenced this issue Oct 18, 2016
@sriv
add skipped datarows to ProtoSpecResult getgauge/gauge#363
90857ee
sriv added a commit that referenced this issue Oct 18, 2016
@sriv
add skippedDataTableRows to ProtoSpecResult #363
c737ce0
@apoorvam
Copy link
Contributor

The message ProtoTableDrivenScenario in spec.proto now has a field tableRowIndex which indicates the table row number against which the scenario in the message is executed. This is implemented here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mahendrakariya @apoorvam