Feature Request Changing the bundled NUnit version

We are currently moving the Test Runner functionality into a package. The built-in NUnit is going to be a separate package referenced by the Test Runner one. So, in theory, you should be able to swap that one with any other NUnit version, but in practice, things might not work as expected if you do that or might not works at all.

The reason is that the NUnit version we use contains some modifications compared to the original:
- it removes System.Web.dll
- changes some internal NUnit APIs to public, so that we could make our own test runner to use instead of their default one (required for dealing with platforms like WebGL, where multithreading isn't supported)
- NUnit did not respect equality overloading, so checking for null on UnityEngine.Object and other things like that were added
- maybe other things I can't remember

I think the version of NUnit we currently use is 2.6.4 and we want to update to at least NUnit 3

 

@ElvisAlistar We currently ship Unit 3.5-ish.

The biggest thing we changed in NUnit was restructuring the execution engine to make it possible to write tests as coroutines (i.e. support for the [UnityTest] attribute). I did look at whether there was a nice way to upstream this but couldn't come up with anything that I thought would be appealing to Charlie and the team. Maybe once it's all packaged up, it'll be easier to figure something out.

 

Hey.
Updating nunit is something that we would like to look into when we have the bandwidth for it. However it is currently unknown for us how feasible it will be to do so and how much will break when we upgrade it. We cannot promise anything yet, but it is on our radar.