Support for Verify

[SabotageAndi]

Types of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• Performance improvement
• Refactoring (so no functional change)
• Other (docs, build config, etc)

Checklist:

• I've added tests for my code. (most of the time mandatory)
• I have added an entry to the changelog. (mandatory)
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[SabotageAndi]

@Bayn Verify is working with this, but the naming of the files isn't right yet.

I think with https://github.com/VerifyTests/Verify/blob/main/docs/naming.md#derivepathinfo we could adjust the generation that it takes Feature title/Scenario title automatically.

Perhaps you can have a look at this?

[baynezy]

Thanks @SabotageAndi - I'll take a look later this week. I really appreciate your help.

[SimonCropp]

shouldnt specflow default to duplicating all attributes from *StepDefinitions over to *.feature.cs ?

[SimonCropp]

@SabotageAndi as a workaround. you can add a partial with the marker attribute to your project

namespace Example.Spec.Features;

[UsesVerify]
public partial class HtmlGenerationFeature
{
}

note you will need one per definition and the namespace and name have to match

[SabotageAndi]

shouldnt specflow default to duplicating all attributes from *StepDefinitions over to *.feature.cs ?

No, it doesn't. The Step definitions are executed at runtime. Some Gherkin tags (@some_tag) are translated to attributes, but not all.

[kaylumah]

@SabotageAndi this looks very promesing, any plans on officially releasing this plugin?