I tried to upgrade to version 2.0.0 yesterday and my tests started, misbehaving, for a lack of a better word.
I've been experimenting trying to find out exactly what's going on, but the only pattern I've found is that the tests just stop after 4 ExecuteAndWaitForSagaToComplete. And by stop, I mean that they do not fail, or pass for that matter, the process just exits. They're listed in the Visual Studio test explorer as if the test wasn't run.
In the explorer view above, the test CreateSubscriptionTest is a parameterized test where each run has 5 ExecuteAndWaitForSagaToComplete. The first 4 are executed and work fine, but then the process just exists before triggering the 5th one.
The test below it, SubscriptionTest is a longer scenario test split into multiple testcases, here the two first testcases complete successfully, having 2 ExecuteAndWaitForSagaToComplete each, then the 3rd method starts followed by the process exiting.
If I run the methods individually they run just fine.
If I step through the tests in the debugger, everything is fine 🤷♂️
Downgrading back to version 1.0.0 resolves the issue.
I tried to upgrade to version 2.0.0 yesterday and my tests started, misbehaving, for a lack of a better word.
I've been experimenting trying to find out exactly what's going on, but the only pattern I've found is that the tests just stop after 4
ExecuteAndWaitForSagaToComplete. And by stop, I mean that they do not fail, or pass for that matter, the process just exits. They're listed in the Visual Studio test explorer as if the test wasn't run.In the explorer view above, the test
CreateSubscriptionTestis a parameterized test where each run has 5ExecuteAndWaitForSagaToComplete. The first 4 are executed and work fine, but then the process just exists before triggering the 5th one.The test below it,
SubscriptionTestis a longer scenario test split into multiple testcases, here the two first testcases complete successfully, having 2ExecuteAndWaitForSagaToCompleteeach, then the 3rd method starts followed by the process exiting.If I run the methods individually they run just fine.
If I step through the tests in the debugger, everything is fine 🤷♂️
Downgrading back to version 1.0.0 resolves the issue.