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
Current agent-js-cucumber only checks previous scenario name to create a unique name for the scenario (appending "[number]" after the scenario name) - guessing this was to account for scenarios with examples.
However, this will make some scenarios have same name if there are few other scenarios that have same name but not placed right after/before.
Example:
Scenario: Test
Given this test has name Test
Scenario: Test2
Given this test has name Test 2
Scenario: Test
Given this test has name Test also
This will report to the reportportal as Scenario: Test
Scenario: Test2
Scenario: Test
Possible/Proposed Fix:
Have a scenario name object that keeps track of what index to append to the end of the scenario name.
Current agent-js-cucumber only checks previous scenario name to create a unique name for the scenario (appending "[number]" after the scenario name) - guessing this was to account for scenarios with examples.
However, this will make some scenarios have same name if there are few other scenarios that have same name but not placed right after/before.
Example:
This will report to the reportportal as
Scenario: Test
Scenario: Test2
Scenario: Test
Possible/Proposed Fix:
Have a scenario name object that keeps track of what index to append to the end of the scenario name.
**Note: that I commented out few codes that was causing me the bug I mentioned in #37
Above change will result in following report to the reportportal
Scenario: Test
Scenario: Test2
Scenario: Test [2]
The text was updated successfully, but these errors were encountered: