Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breaking change in SpecFlow 3.3.57 #49

Closed
DanielVuurboom opened this issue Jul 22, 2020 · 1 comment · Fixed by #50
Closed

Breaking change in SpecFlow 3.3.57 #49

DanielVuurboom opened this issue Jul 22, 2020 · 1 comment · Fixed by #50

Comments

@DanielVuurboom
Copy link
Contributor

DanielVuurboom commented Jul 22, 2020

Describe the bug
When upgrading SpecFlow to version 3.3.57 the constructor for ScenariInfo is changes from:
public ScenarioInfo(string title, string description, params string[] tags)
to:
public ScenarioInfo(string title, string description, string[] tags, IOrderedDictionary arguments)

This results in a failure to create the
private static readonly ScenarioInfo EmptyScenarioInfo = new ScenarioInfo(string.Empty, string.Empty);
in Allure.NUnit/AllureSpecFlow/PluginHelper.cs

To Reproduce
Run any scenario with this package combination:

    <PackageReference Include="Noksa.NUnit.Allure" Version="3.1.0" />
    <PackageReference Include="Noksa.NUnit.SpecFlow3" Version="1.1.5" />
    <PackageReference Include="NUnit" Version="3.12.0" />
    <PackageReference Include="NUnit3TestAdapter" Version="3.17.0">
    <PackageReference Include="SpecFlow" Version="3.3.57" />
    <PackageReference Include="SpecFlow.Tools.MsBuild.Generation" Version="3.3.57" />
    <PackageReference Include="SpecFlow.NUnit" Version="3.3.57" />
@DanielVuurboom DanielVuurboom changed the title Breaking change in SpecFlow 3.1.97 Breaking change in SpecFlow 3.3.57 Jul 22, 2020
@Noksa Noksa closed this as completed in #50 Dec 11, 2020
@Noksa
Copy link
Owner

Noksa commented Dec 11, 2020

You can find new packages on the nuget.org

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 a pull request may close this issue.

2 participants