CharliePoole
CharliePoole
The AsyncTestEngineResult returned from RunRestsAsync never shows as completed. This error doesn't actually affect how we currently work, since we don't use the RunAsync method in the console runner. However,...
This feature was first developed as "Engine Extensibility" so the implementation is embodied in an engine service. This makes it next to impossible to use extensibility in other places, like...
@ChrisMaddock @mikkelbu @rprouse @jnm2 I'm calling this a question, but I mean it as a question we are asking ourselves. Here's a rough outline of what I want to try...
There appears to be a race condition between two processes detecting that the TCP connection has been closed. Either we should unload the second level test runner or perhaps not...
I'm writing this to replace issue #858. That issue has become cluttered with a lot of confusing comments... many of them my own. :-( The confusion largely arises because it...
Currently we build into a set of bin directories according to the target runtime... net20, netcoreapp3.1, etc. Then we Publish the projects into the _same directories_. This can be very...
This is a soft prerequisite to #1044. That is, we could work around it in somewhat complicated ways... but let's not! Our .NET 5.0 builds contain unguarded calls to Windows-specific...
Question for the team for V4... Currently, `TestPackage` is defined in the `nunit.engine.api` assembly. I'm working on issue #889 to remove some confusion about the constructor for `TestPackage` and simplify...
@CharliePoole commented on [Sat Dec 12 2015](https://github.com/nunit/nunit/issues/1134) > Users need a way to install extensions, enable and disable them and update them. This could be a separate program or a...
@nunit/engine-team Looking for input on where we should send notices. What has been done in the past? What do we want to do in the future?