RawRabbit uses the .NET CLI to execute it's tests. Since the integration tests uses the same message broker and also the same types of messages, the tests in the suite needs to be executed in sequence in order to secure that the tests doesn't interfere with each other.
Previously, this has been successfully done by providing the parallel flag to the command
dotnet test -parallel none
However, this option is no longer available. After talking to the xUnit team, they recommended using xunit.runner.json and set parallelizeTestCollections to false.
This helps with running the tests in parallel, but the test suite still fails. Looking at the consumers, channels and connection in the management plugin, I can confirm that there more of them than I expect.
The problem does not occur if I run the test one at a time.
RawRabbit uses the .NET CLI to execute it's tests. Since the integration tests uses the same message broker and also the same types of messages, the tests in the suite needs to be executed in sequence in order to secure that the tests doesn't interfere with each other.
Previously, this has been successfully done by providing the
parallel
flag to the commandHowever, this option is no longer available. After talking to the xUnit team, they recommended using
xunit.runner.json
and setparallelizeTestCollections
to false.This helps with running the tests in parallel, but the test suite still fails. Looking at the consumers, channels and connection in the management plugin, I can confirm that there more of them than I expect.
The problem does not occur if I run the test one at a time.