CharliePoole

@OsirisTerje How about something like vs-followup as a label (or other words that make sense to you) That would eliminate strangeness (to me) of having both a closed: and a...

The adapter does not write to stderr or stdout. A quick look at the code will show that and it's obvious that it can't since it's not a console program....

@cklutz I sent you an invitation to become a contributor to NUnit. It looks like you have already done several things in your fork, which are outstanding issues in this...

~~@cklutz If you are willing to take this issue on, I'll assign it to you. You said you don't have much time, but I notice you already have the code...

@cklutz Whoops! I posted on the wrong issue - reposted the comment on #97!

I believe this occurs in the adapter because of a fundamental difference in how tests are found when using the adapter as opposed to the NUnit gui. With the Gui,...

I meant the following version after 2013. I doubt that ms would substantially change how they deal with tests in the vs2013 context. It's also possible that we will change...

In NUnit 3.0, random parameters are repeatable, provided the same initial seed is used. This is a command-line argument for the console runner. We could do the same thing for...

I increased the priority from low to normal in the context of 3.0. i agree it's 3.0 only.

I created nunit/nunit3-vs-adapter#97 to track this for the 3.0 adapter. Despite having agreed with it's being 3.0 only last week, I'm not really happy with closing it here. It seems...