Myujth

We're starting to use cucumber (Java) and really liking it but Cucumber seems to completely fail at a very important case:

Basically I have a scenario that runs for a given logged in user, I need to literally run all the same tests with a different type of logged in user.

Then after that I need to run most of the exact same scenarios with a user logged in with a different role (multiple roles with overlapping authority)

This would be clean and trivial with a Background outline functionality, but that seems to have been denied years ago ( https://github.com/cucumber-attic/gherkin/issues/56)

I know this has been asked before but I keep turning up very old threads (some 6 years old!) with no answer other than "duplicate all your scenarios".

Duplicating hundreds of Scenarios is a failure on every front, it makes the test base unmanageable (a change in one scenario needs to propagate to multiple duplicates) . It fails in the core communication goal of cucumber as we get a huge bloat of feature files making it harder to know what the app is doing and what we're testing.

in the 6 years since the first complaints is there any reasonable way to manage this?

at this point I'm tempted to remove the background and move it into each scenario and use scenario outlines, it's ugly and the tests no longer read as cleanly but at least I don't need to duplicate scenarios.

Then after that I need to run most of the exact same scenarios with a user logged in with a different role (multiple roles with overlapping authority)

You want to test an authority but are instead testing roles. It seems to me that this is causing most of your problems. As roles are usually configured you may be able to leverage this system.

Given a customer service rep with the authority to grant refunds 
 And a customer reports a problems with the PX-11 Widget
 When customer service resolves the problem by granting a refund
 Then problem ticket is closed
 And a refund request is lodged with finance

In the given step you create a new role for the customer service rep that can grant refunds.

If you have concerns that roles may affect each other in strange ways you should try to solve and test that at a lower level. It shouldn't be a concern that comes back in your acceptance tests.

If you are however unable to do so you may want to consider any of the three options below. It will keeps the gherkin readable at the cost of some added test complexity. But this complexity is indicative for a problematic system.

1. Creating multiple customer service reps with the requested authority in addition to the other authorities you are concerned about. Then in each follow up step you make all reps do the specific action.




2. For each test in addition to requested authority picking one or more authorities at random.




3. Pick a role with the required authority at random.