-
-
Notifications
You must be signed in to change notification settings - Fork 46
InitializeAsync is not called for Scenario tests #655
Comments
@DanHampl thanks for raising this. I'll look into it. |
Hello - do you have an update here? |
@WTobor I'm afraid not. It's on my radar, but I've had no time to look into it yet. |
I think I just ran into this myself and it's kind of blocking me, would you take a PR for this if I can figure out what the problem is? |
@redoz sure, please feel free to send a PR. |
@adamralph I have to see if I can fix it first 😄 |
@adamralph So apparently I need learn how to read better, because I thought this was about IAsyncLifetime on the collection itself and that appears to work fine. So I'm going to investigate why it doesn't work in my actual project, I guess I made a mistake somewhere. 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 class? |
Sure, I'll happily take a look. |
FYI I've started the ball rolling by pushing a failing test for this to https://github.com/adamralph/xbehave.net/tree/async-class-fixture |
Version(s)
"2.4.1"
To reproduce
Expected behavior
IAsyncLifetime will be called for [Scenario]
Actual behaviour
InitializeAsync is not called for [Scenario]
Workarounds
Call InitializeAsync from the test itself
Additional context
Works flawlessly for [Fact]
The text was updated successfully, but these errors were encountered: