Adam Ralph

> Is #566 on hold waiting for xunit3? @redoz no, it's not waiting for xunit3. It's something I started a while back, but didn't have time progress with any further....

Right now (when I get back from holiday) the focus is getting xbehave 2 (based on xunit 2) on a par with xbehave 1 but this is definitely a good...

Also see proposed use case by @wangvnn over at https://github.com/xbehave/xbehave.net/issues/251#issue-72346658

Need to think of another way to do it. The example shown would close the method with the type parameter being `System.Type` and will always do so unless we special...

We could introduce a special type as a wrapper for types. E.g. ``` C# [Scenario] [Example(typeof(ExampleType))] [Example(typeof(ExampleType))] public static void MungingWidgets(TWidget widget) where TWidget: IWidget, new() { "Given a {0}"...

Not possible until the net452 target goes away.

@DanHampl thanks for raising this. I'll look into it.

@WTobor I'm afraid not. It's on my radar, but I've had no time to look into it yet.

@redoz sure, please feel free to send a PR.

> Meanwhile, do you want a PR for the tests I added that makes sure that IAsyncLifetime is called correctly on collection fixtures that are not injected into the test...