All geek questions in one place

Why use TestDriven.net when you have Resharper?

As far as I can tell, TestDriven.net is focused on providing direct access to test runs from Visual Studio. However, Resharper, being a more general tool, also provides this functionality. If you are using Resharper, does it make sense to use TestDriven.net?

+3
source share
6 answers

If you have a resharper, then no, you probably don't need it. If you do not, this is a great free tool.

+9
source

TestDriven.NET "" "Test Test (s)". , , , (, DateTime ..), unit test.

ReSharper , TestDriven.NET;-) , [Test] .. .

+8

TestDriven.NET :

  • . , . TestDriven.NET "n , m failed, x skipped" . , .
  • Console.Write(). . , . , .
  • , , , . , REPL # (, , , Mono # REPL, :).
+2

TestDriven.net Resharper: , .

+2

Resharper , VS, TestDriven.net. .

+1

TestDriven.net , ReSharper . , , TestDriven.net ReSharper .

ReSharper , , , ReSharper , .

After using ReSharper much more, I would say that it is good to run many unit tests and display a combined result when more than 1 test fails. I still think TestDriven.net is great for running a single unit test, or when you run a test so often that only 1 or 2 tests fail.

+1
source

Source: https://habr.com/ru/post/1792901/

More articles:


All Articles