Skip to content

Resolves #238 - adding a Reqnroll integration#262

Merged
craigfowler merged 8 commits into
masterfrom
238-reqnroll-integration
Jan 18, 2026
Merged

Resolves #238 - adding a Reqnroll integration#262
craigfowler merged 8 commits into
masterfrom
238-reqnroll-integration

Conversation

@craigfowler

Copy link
Copy Markdown
Member

This adds an integration for Reqnroll 2.0.0+ to CSF.Screenplay.
I have chosen explicitly not to support Reqnroll 1.x, because of a troublesome namespace switch.

Also write the MSBuild for code-sharing and update the READMEs.
I'd forgotten to exclude the bin and obj directories.
Also, a place where I'd used the wrong compiler symbol.
These are presently a copy-paste of the SpecFlow ones.
That should be fine.  I also want to test Reqnroll across versions,
as it has received a number of upgrades since v1.0.0.
I'll add that in a future commit.
Namespace changes from v1.x to v2.x mean I can't
support both without compiler symbols and thus
building two Reqnroll packages.  Reqnroll v1.x was
very short-lived (3 months) so I'm comfortable
electing not to support it.
The cause of this and the remediation is documented
on this pull request for Reqnroll:
  reqnroll/Reqnroll#1004

In short:  I mustn't attempt to resolve ScenarioContext
from that extension point.  Instead resolve ScenarioInfo,
which is all I ever needed anyway.

The improved logic works with both Reqnroll 2.0.0+
and the legacy SpecFlow.
@sonarqubecloud

sonarqubecloud Bot commented Jan 18, 2026

Copy link
Copy Markdown

@craigfowler
craigfowler merged commit 47b3e03 into master Jan 18, 2026
3 checks passed
@craigfowler
craigfowler deleted the 238-reqnroll-integration branch January 18, 2026 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant