Add Before/After attributes for unit-test.

[laneser]

Sorry for empty description.

Those are hooks attributes for unit-test.

please reference for specflow http://specflow.org/documentation/Hooks/

[ttutisani]

Hi. Why do you think this feature is necessary? What's the use case?
Nobody has asked about this yet. So I assume you need it.
Can you please describe for what you need it specifically?

[laneser]

The project is a very good quick replace solution for specflow when we moved to dotnet core.
But the hook attributes in specflow does not support in the project.
So I think this is a good feature for the project.

[ttutisani]

This framework does not intend to replace specflow. That alone will not be enough to have this feature considered. I hope this does not come as a big frustration.
Can you please provide an example of a feature and scenario which require before/after methods?
If you can explain the need for it from feature/scenario standpoint, that can help in this process a lot.
Thank you!

[laneser]

For those unit-test which need initialization or destruction functions,
such as database creation and cleanup, we put those code in [BeforeScenario] and [AfterScenario].

I will not feel frustrated if you reject the feature, then I will use my forked project.
Thanks for your patient!

[ttutisani]

Thanks for clarifying!

Initialization code should go into constructor of the tester class (one that derives from Feature). Or, if you have an advanced case, you can use Collection Fixture from Xunit, which supports both setup and tear down methods. You can read about this here for example: https://stackoverflow.com/questions/12976319/xunit-net-global-setup-teardown

At this point, I would have to restrain from merging this feature. If I see a need for such functionality in the future, clearly from feature/scenario (Gherkin) test standpoint, then I will come back to this.
Sorry!

But if you think I'm misunderstanding something, please do let me know.
As I said, for what you described, Xunit has better ways (Collection Fixture), so I don't think I need to support something in addition.

[ttutisani]

Output is null because I assign to Output after constructor executes.

But, if you want Output to be not null, simply add ITestOutputHelper as your constructor parameter.
When constructor runs, use the parameter value, not Output property.

e.g.:

public sealed class MyFeature : Feature
{
    public MyFeature(ITestOutputHelper output2)
    {
        // output2 is not null, Output is null.
        var type = output2.GetType();
    }
}

[ttutisani]

Closing as out of scope. Thanks anyway for the effort!