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 using Screenplay with SpecFlow, the IDs of the features and scenarios are auto-generated GUIDs. It is pointless to include these GUIDs in the reports.
Anything which writes reports should have some manner of indicating that a Feature/Scenario is auto-generated. When this is detected in the report, the reporting mechanism may choose to suppress them.
The text was updated successfully, but these errors were encountered:
I have a first stab of this done, but I'd like to rework it a little so that I don't need to explicitly configure the reporter differently.
What I need is to extend the event which is raised when a test runner begins a scenario. It's at that point it should be able to pass (via event args) flags which indicate the identifiers which were auto generated.
When using Screenplay with SpecFlow, the IDs of the features and scenarios are auto-generated GUIDs. It is pointless to include these GUIDs in the reports.
Anything which writes reports should have some manner of indicating that a Feature/Scenario is auto-generated. When this is detected in the report, the reporting mechanism may choose to suppress them.
The text was updated successfully, but these errors were encountered: