Cross Platform Scenarios / Shared Location with Feature Files

[TesterEric]

My VS solution contains the following .NET projects:

• GherkinSuites (net8.0, shared location for feature files that needs to run on Windows as well as Linux )
• GherkinSuites.Runner.Windows (net8.0-windows, test runner for scenario running on Windows)
• GherkinSuites.Runner.Linux (net8.0, test runner for scenario running on Linux)
• TestStepDefinitions.Lib.Windows (net8.0-windows, implementation of Windows steps only)
• TestStepDefinitions.Lib.Linux (net8.0, implementation of Linux steps only)

Furthermore I am using reqnroll 3.x

I want to run these scenarios as follows:

dotnet test GherkinSuites.Runner.Windows.dll
dotnet test GherkinSuites.Runner.Linux.dll

Where both dlls (should) contain scenarios from the shared GherkinSuites project.

How can make sure that generated code behind files from feature files (GherkinSuites project) end up in the 2 runner projects so that I am able to run the tests with above commands?

The issue is that reqnroll recognizes the steps from TestStepDefinitions.Lib.Linux, but not from TestStepDefinitions.Lib.Windows.

What I want to achieve one shared location for feature files and separating the test step over multiple projects based on target framework.

Any help is appreciated.

[clrudolphi]

Keep in mind:

1. In order for your 'Runner' project to include the step definitions from separate projects configure the runner project as described here to include external step assemblies.

2. There is no means available for a Reqnroll project to reuse features from another project.

An alternate approach to consider is to consolidate your scenarios and tag them and then use tag filtering when executing on each specific platform.

[TesterEric]

@clrudolphi , I refactor the solution a bit based on your comments:

My solution has 3 projects

• project: scenarios (target framework net8.0 and net8.0-windows) with project file:

	<ItemGroup Condition="'$(TargetFramework)'=='net8.0-windows'">
		<ProjectReference Include="..\windows.steps.csproj"  />
	</ItemGroup>

	<ItemGroup>
		<ProjectReference Include="..\linux.steps.csproj" />
	</ItemGroup>

• project: linux.steps (target framework net8.0 and net8.0-windows)
• project: windows.steps (target framework net8.0-windows)

The scenarios project has reqnroll.json containing:
"bindingAssemblies": [ { "assembly": "linux.steps" }, { "assembly": "windows.steps" } ]

Furthermore project has one feature file containing:

@windows
Scenario: Run on Windows

	Given There are multiple environments
	When I build this scenario for a Windows environment
	Then The scenario should run on this environment

@linux
scenario: Run on Linux

	Given There are multiple environments
	When I build this scenario for a cross platform environment
	Then The scenario should run on this environment

When building the following warning appears:
The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled.

Any help would be appreciated

[clrudolphi]

The scenarios project should have Project References to the step assembly projects in order for their assemblies to be copied into the Scenario project's output directory.

[TesterEric]

@clrudolphi , I have updated my previous comment. Also when adding these project references to the step assembly projects the project binding could not be discovered. I have a cross platform environment with a shared project containing feature files of which scenario can run on a Linux platform and Windows platform. The steps files are implemented in 2 separate projects targeting net8.0 and net8.0-windows for the linux steps and net8.0-windows only for Windows steps.

Any help would be appreciated

[clrudolphi]

The error message appears to be the one issued by the Reqnroll extension for Visual Studio. If that is true please post the full stack trace that you will find in the Output window of VS (selecting the Reqnroll drop-down of the Output window).

What happens when you build or test this from the command line?

[gasparnagy]

Sorry to just sneak into the discussion, but linked feature files are supported since v3.3, you just need to enable ReqnrollUseIntermediateOutputPathForCodeBehind. See second note at https://docs.reqnroll.net/latest/installation/setup-project.html#choosing-your-test-execution-framework