hello,

I've got a small suite of BDD tests, for an Aspnetcore server connecting to a RavenDb database. The tests work fine under Visual Studio and the dotnet cli, and will pass under NCrunch when first run. Under NCrunch however, the tests will quickly start failing, with the RavenDb server timing out, even without code changes (I'm not sure what else is going to prompt the tests to be re-run).

As far as I can work out, this is typically a symptom of tests running in parallel, and the test context not being disposed of correctly, which can then overload the RavenDbTestDriver. Is there a way I can get NCrunch to recognize that Reqnroll tests should be run in sequence, and ensure that I am disposing of things correctly after each test?

I have made use of the ExclusivelyUses attribute for non-Reqnroll tests, which seems to work well there, but does not seem to have an effect on Reqnroll.

I am using Reqnroll 2.3.0 + NUnit 4.3.2 + RavenDB.TestDriver 7.0.0 + Microsoft.AspNetCore.Mvc.Testing 9.0.2

In the beginning I was trying to use a base class that implemented IDisposable. I hoped that this meant that everything would be disposed at the end of the test execution. I was incorrect in my assumptions about how this would work, and this would cause NCrunch to start failing tests with RavenDb timeouts.

I'm currently using a base class and trying to take advantage of the "BeforeScenario" and "AfterScenario" attributes to control initialization and teardown of tests. A RavenDb IDocumentStore gets created during intialization and then disposed of during teardown. This pattern has seemed to work well outside of using Reqnroll (using the equivalent NUnit attributes "SetUp" and "TearDown").

This pattern unfortunately does not seem to work well with Reqnroll. Almost any code changes in the solution will cause Ravendb timeout failures in the Reqnroll tests.

Disabling parallel test execution does stop the timeout failures, but at the expense of much longer execution times.

Is there any way to specify parallel or sequential execution at the project level?

It looks like applying "ExclusivelyUses" at assembly level is the only thing that is going to work for tests using Reqnroll at the moment. That seems to have fixed the problems I was seeing with parallel test execution. Thanks for your help.