CharliePoole
CharliePoole
When the option is used with the console runner, the output file contains only the text output written by the test. All other output, such as the test report, is...
I encountered this as an apparent TestCentric GUI error when running more than one assembly in an AppDomain, i.e. the equivalent of either `--inprocess` or `--process:Separate` together with `--domain:Single`. It's...
Historically, the console runner has used "Off" as the default for internal trace logging. An argument can be made that "Error" or even "Warning" is a better choice and that...
@nunit/engine-team @nunit/core-team Currently using C# 12. Does anyone see a reason not to do this for V4?
This seems to be a regression. See #1322. Presently, it only appears when using the standard runner with agents and not using the netcore runner. Since only an empty agent...
`TestAssemblyLoadContext` makes use of a custom resolver, `TestAssemblyResolver`, to locate assembly references. Internally, the resolver uses a Strategy pattern, under which multiple strategies are tried until the assembly reference is...
For beta.1, loading of extensions was disabled for the .NET 8.0 build of the runner, because it wasn't working correctly. This should be restored for beta.2.
**UPDATED 19 Oct 2025** Because NUnit Extensibility was designed for the engine, the `ExtensionAttribute` supports a property 'EngineVersion`, which is checked by `ExtensionManager`. However, the V4 update to the extensibility...
Inspired by Terje, I'm going to use issues labeled "Release Plan" for... wait for it... Release Planning! Unfortunately, I didn't do this before the just-released 4.0.0-beta.1, so I'll start with...
This would be a pluggable agent for use in running tests in-process. It would target both runtimes for which the console runner is built. It would be bundled as a...