3 ms·
This is pretty cool and I was excited to hear about it. But this release also changes the way unit testing integrates with the tooling, so now my suite of 1000
by danek 10y ago
This is pretty cool and I was excited to hear about it.
But this release also changes the way unit testing integrates with the tooling, so now my suite of 1000+ nunit tests won't run via the 'dotnet test' command, nor in visual studio 2017.
If not for that, we would have upgraded today. Eventually the nUnit team will release a test runner that works with the new tooling, but in the meantime, we will stay on preview2 of the tooling & vs2015 where our tests work.
- Sacho 10y agoIs the change documented anywhere? I looked through all the release notes and couldn't find it. It looks like it wasn't this release that changed the testing. The comments about nUnit not working are from November / January / February: https://github.com/nunit/dotnet-test-nunit/issues/91 https://github.com/nunit/dotnet-test-nunit/issues/91 https://github.com/nunit/dotnet-test-nunit/issues/101 https://github.com/nunit/dotnet-test-nunit/issues/101 https://github.com/nunit/nunit3-vs-adapter/issues/305 https://github.com/nunit/nunit3-vs-adapter/issues/305
- danek 10y agoI think you are right, the change likely happened in one of the preview versions leading up to this release. I didn't notice any documentation on it for any of the releases, though I could have easily missed it.
- mihular 10y agoYep, they are working on it, but won't say when it'll be released.