Closed grey-rain closed 1 month ago
Before fixing it I would like to see how such cases are represented in native native Serenity report. I assume it could be done intentionally to keep names consistent and distinct data driven tests by parameters.
@Invictum you're right, it appeared to be native Serenity behaviour.
I'll close current pull request for now and add this info to the original ticket. We'll decide what to do next in there.
Issue
Scenario Outlines do not take parameters passed into account when build names.
Solution
Implemented util to build final name on integration side. TestOutcome class does not contain desired data in the way we'd like.