Clever Geek Handbook

Pros and cons of unit testing with t #

I recently came across T # . Sounds like a good concept, but I'm wondering if it's worth switching from nUnit to this? I like professionals, but I hate opponents, so I'm still not sure.

Pros:

  • specialized language for unit testing (keywords)
  • relative statements
  • compile time warnings
  • focus on testing intent

Minuses:

  • Lack of (integrated) tool support.
  • is it still beta?
  • not used by many

(Don't forget to update the list)

+2


source to share


2 answers


I know this might not be a strong argument, but looking at some of this code example it just gave me a shiver. It seems like they are mostly introducing new keywords as syntactic sugar to replace regular syntax like Assert(x, y)

or even whole methods. I dont know. It just looks ... wrong.



0


source


In my experience, the most important factor in successful unit testing is ease of use - you have to easily write and run tests from visual studio, otherwise it will become a big problem and will be reset from the first missed deadline.
This is one of the reasons I only use the frameowrk block diagram, which has good integration into VS - either built it (MSTest) or with third party tools (NUnit, XUnit, etc.).



T # looks very promising, but it has VS integration. I would not touch him.

0


source






More articles:


All Articles