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
Scenario outlines are reported differently across various cucumber JSON dialects. Some interpolate the example table name and the row number into the scenario's ID (Cucumber-Ruby, Cucumber-JS). Others - into the scenario's name (Behave).
We should carefully review different dialects and implement an algorithm to extract such IDs and convert them into the test's parameters or embed them into fullName to keep each test separated.
The text was updated successfully, but these errors were encountered:
Scenario outlines are reported differently across various cucumber JSON dialects. Some interpolate the example table name and the row number into the scenario's ID (Cucumber-Ruby, Cucumber-JS). Others - into the scenario's name (Behave).
We should carefully review different dialects and implement an algorithm to extract such IDs and convert them into the test's parameters or embed them into fullName to keep each test separated.
The text was updated successfully, but these errors were encountered: