I've just upgraded a project with extensive unit tests from 5.4 to 5.6 and the changes to unit testing feel like a backwards step to me. In 5.4 we had a unit test runner window that was: - moderately fast - had search filters for finding tests by name - had filters to hide passing/ignored tests - ran on recompilation In 5.6 the external tools are dropped and we have new internal tooling. I was excited to see this! However Unity seems to have merged the unit and integration aspects of the old tools, and the new UI leads a lot to be desired: - it's achingly slow, probably because it's serialising a bunch under the assumption my tests will touch the scene hierarchy. However they do not. - the UI has no filtering, so a single fail in hundreds of tests is hard to find - it no longer runs on recompilation, which is a blessing in disguise considering the speed Ok, I thought, maybe this is now an integration-style tool and I should look elsewhere for a unit-focused option. However monodevelop on OSX still can't run the unit tests out of the box, failing instantly with an invocation error. I even went so far as to try and get the old tools test runner UI running under 5.6, but it does not seem willing to cooperate with 5.6's version of nunit. I hope you understand that it's infuriating to lose so much functionality. I can see how unittesting monobehaviours is now more manageable, but people like me who were writing unit tests in unity's previously preferred manner have had their workflows greatly altered. I'm looking to understand more about where the new tools are heading, why these decisions were made, and how I can improve my workflow. Can anyone help me?