CharliePoole

Summarizing some points from nunit/nunit... 1. The NUnit team is somewhat concerned about the idea that unstable NUnit 3.0 beta could be part of a stable overlay for gentoo. As...

@Heather OK, I hear you about the overlay not being your main repository. That makes a little more sense. Bear in mind I've nevr seen an ebuild before, so my...

@Heather Re the three points... 1. It's good it's not stable. If only the NUnit provided indicated what it's true version of origin is, then I'd be happy. 2. I...

So I understand now (didn't earlier) that this is the output from the execution of your ebuild. It's similar to what we put in our installations. Differences are for two...

@imakowski Based on the exeception being thrown in `NUnit.Framework.Api.FrameworkController`, I suspect this is a framework rather than a console problem. Did it work in versions of the runner prior to...

@tshcherban Are you running the NUnit ConsoleRunner or the .NET Core ConsoleRunner? Unfortunately, we call them both `nunit3-console.exe` but they come in different packages.

I'm afraid that's the point: there are two different runners in this repo, with different capabilities and the same executable name. Probably a bad decision, but we're stuck with it...

This is a great idea. I'm going to use it in my own stuff! I was always concerned about the more hard-coded approaches, because they are harder to adjust according...

Having an Assert inside your TestCaseSource method is not valid because NUnit is not executing a test at the point where the method is called. It would take some debugging...

I see that this is a problem for you. What I'm not able to understand is why it was not always a problem. When used outside a test, an NUnit...