The unit test runner has always worked well for me, but latest version seems to be extremely buggy. All these issues are for an nUnit test project we have. We are running version 2017.2, maybe these issues are known and being worked on? I can't imagine we are the only ones experiencing this and there is nothing out of the ordinary about our test setup for nUnit.
Incorrect nesting of tests in the Unit Test Explorer where there is an Nunit SetupFixture, some TestFixtures seem to be nested under it, others not, there doesn't seem to be any reason why you would nest tests when a SetupFixture applies to all tests in a namespace anyway?
Unit Test Explorer not showing the correct list of tests, even after hitting Refresh, only option being to close the solutions and open it again
Unpredictable behaviour when trying to run tests at a Fixture level. This has worked fine for me in the past but is causing big problems at the moment. Unless I specifically select the unit tests I want to run in the unit test explorer I can't trust what will happen when I try to run all tests in a certain TestFixture, mostly all the Tests in the full project seem to start to run in some kind of strange mode where every test is it's own session with OneTimeSetUp being called once per test.