IPC Server activation on dotnet test
Closed this issue · 0 comments
Refactoring is needed to properly support dotnet test as the test runner, due to differences in NUnit extension activation. Currently the IPC server is started on the extension so clients can connect and receive test events - this works fine when using the nunit-console runner as it's only activated once at the start of a test run. In dotnet test however extensions are activated for each assembly (or some other condition) and this bottlenecks the test runs as numerous IPC servers block while waiting to startup.
To deal with this we should reverse the way events are sent - the extension becomes the client and NUnit.Commander will operate as the IPC server. This way any changes to the extension activation or threading model will have no effect on test runs.