You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a scenario with a table with many rows, the report shows the same Scenario Heading for each row of the table. This causes confusion as to which row had a failure in order to troubleshoot the issue.
We sometimes have over 100 rows in our CSV files. Troubleshooting can take a very long time narrowing down which row had the failure.
In IntelliJ, when the test runs, the scenario heading has a suffix _<row-number> added at the end. The XML report does the same. It would nice if we can get the same functionality.
When running a scenario with a table with many rows, the report shows the same Scenario Heading for each row of the table. This causes confusion as to which row had a failure in order to troubleshoot the issue.
We sometimes have over 100 rows in our CSV files. Troubleshooting can take a very long time narrowing down which row had the failure.
In IntelliJ, when the test runs, the scenario heading has a suffix
_<row-number>
added at the end. The XML report does the same. It would nice if we can get the same functionality.Sample:
XML Report
Json Report
The text was updated successfully, but these errors were encountered: