I understand that all scenarios in gherkin feature file should have unique functionality. How do we treat scenarios which share one or more user story But not All while other scenarios in the same file are unique.
cc: @k.joseph
there a few ways to do this such as through use of hooks, an example exists at: openmrs-contrib-qaframework/LoginSteps.java at master · openmrs/openmrs-contrib-qaframework · GitHub
A step from one file which isn’t unique will be reinvoked from the previous step definition/implementation. in other-wards, if you reuse a step, you can only have one definition of its automation per run
As per say do we then show that shared step in the next scenario in the feature file
no need to tag any shared step, just reusing it by its name
1 Like