featureContext returns null value for variant about specflow.contrib.variants HOT 2 CLOSED

Hi, although you are able to set 'variant' tags at the feature level, the intention was to always treat these scenario variants and not feature variants. i.e. the scenarios are run per variant. The way it's done under the hood to achieve this directly works with scenarios and would be a complete overhaul if we had to support variant features. The tagging of the features is just to simplify tagging all individual scenarios.

There's also potential limitations on the unit test frameworks this package supports, for example if we're talking about a simple unit test then MsTest allows a DataRow attribute on a method (scenario) and you could drive variants that way, but you can't do the same at the class level (feature).

Feel free to fork the repo if you think there's a way to achieve your need. But on my analysis this won't be possible.

from specflow.contrib.variants.

Thank you for your response.

I had a quick look at the src code and from what I could see I think I agree with your analysis.

I used BeforeFeature hooks for initial Appium driver instantiations along with isFullReset=false and isNoReset=true capabilities set.

I was looking at using SpecFlow+ Runner along with Targets but there are issues getting it to work in any IDE on macOS which is why I switched to NUnit.

I guess due to this, I will try and move my Feature hooks to the scenario level.

Anyways, cheers for the explanation.

from specflow.contrib.variants.