Hello,

I'm working on tests for an app with a lot of moving parts. Currently, I do my setup in the Given step, where the tests specify which parts of the app should be set up. The setup takes some time and is parallelized (as it's just the setup of different services, DB, etc.). Multiple setups can not be run in parallel, as there are some dependencies and race conditions to deal with.

As is right now, this is quite inefficient, as extra time is spent waiting for features that are not yet set up, while they could all be running at once.
I thought of the following solution so far:

1. in before_all, check all scenarios
2. find Given steps that match the setup
3. for each setup step, build a unique list of features
4. run setup for all features (in before_all

My question: Is there a supported way of achieving this?

I found that the Context holds a (private) reference to the Runner class, which should be able to access all the Scenarios. I though of the following solution so far:

1. in before_all, obtain scenarios from the Runner
2. find Given steps that match the setup
3. for each setup step, build a unique list of features
4. run setup for all features (in before_all
   But this entire solution feels more like a workaround.

An example of the kind of scenarios I am using:

Scenario: Example 1
    The app has the following features enabled:
      | feature |
      | foo       |
      | bar       |

Scenario: Example 2
    The app has the following features enabled:
      | feature |
      | foo       |
      | goo      |