Reqnroll migration with shared code in a nuget package

[joelransom]

In our organization we have many solutions with each having an integration test (Specflow) project. We want to gradually migrate from Specflow to Reqnroll. However, we have a project that is shared to all the other projects via a nuget package. This shared project contains some shared Specflow steps that all projects use. When upgrading a project to Reqnroll, however, those shared steps are no longer recognized. (i.e. they show up as undefined). (To be clear, I'm describing scenario where the shared project has not been updated, and the project that consumes the shared project has been updated.)

I don't want to be in a situation where if we update the shared project, we then have to update all the other projects at once.
I haven't attempted to solve this yet, as I could possibly break things in the process. I'm wondering if this is a familiar scenario with a suggested solution.

Regards, and thanks.

Joel

[olegKoshmeliuk]

check if you have reqnroll.json with CopyToOutputDirectory Always attribute.

{
  "$schema": "https://schemas.reqnroll.net/reqnroll-config-latest.json",

  "bindingAssemblies": [
    {
      "assembly": "Automation.Common"
    }
  ]
}

And shared nuget must be using Reqnroll too.

[joelransom]

Many thanks for the response, I appreciate your time.

And shared nuget must be using Reqnroll too.

This is perfectly reasonable, and goes to the heart of my question. If shared nuget is using Reqnroll, when I update the package in another project, will that project also need to use Reqnroll from that point forward? If so that's fine, just want to set expectations appropriately.

Edit: we have a workaround that will get us going. We are simply not going to rely on shared steps until the migration is complete. If we had a lot of shared steps this might not be a viable solution, but it's doable for us.