CharliePoole
CharliePoole
Working on #2695 I realized I'd opened a rather large can of works around the display of warnings. I'm using this issue to try to summarize the problems and figure...
For a long time, I've been thinking that the framework successfully cancels tests but doesn't report them as cancelled. That's what issue #166 was all about. I don't know if...
Implement Exclusion groups of tests such that only one test in a group may run at a time.
This release appears to have been done manually, rather than through the automated release procedure used in earlier releases. It doesn't include the zip, msi or chocolatey packages.Several `snupkgs` have...
It's considered unsafe and is going away. See https://github.com/dotnet/designs/blob/main/accepted/2020/better-obsoletion/binaryformatter-obsoletion.md. I've started work on this for my own engine (TestCentric/testcentric-engine#127) and I expect that the changes would apply almost directly to...
In resolving issue #1182, I experimented by actually allowing an assembly targeting .NET Standard 2.0 to be loaded by the engine. In the case of that issue, it was not...
This applies to the nuget package. The documentation at https://docs.nunit.org/articles/nunit/getting-started/installation.html assumes that the package will be installed in the packages folder. This is no longer true. I'm filing this for...
I'd say this is fairly minor and depends on the policy of each project regarding spelling of the text in user issues. My own policy in the engine project (and...
I'm not sure if this is considered in-scope for the project, but I'll throw it out there anyway. Most of my projects use a recipe I created. When working on...
Currently, we use the single failure message created for compatibility in order to display the result of a test using multiple asserts. It should use the actual result of each...