Interested in a
Personal Demo ?


Name* :
Please Enter your Name
Company E–Mail* :
Please Enter a Valid Email

Testimonials


We need to maintain legacy applications that were not built to facilitate unit testing. Without Typemock we would be completely unable to effectively test these applications. Typemock boosts productivity because you do not have to explicitly code from the ground up with testing in mind, which can be difficult to handle. Typemock has been able to cover up the coupling and dependency sins that we all have leaked into our applications from time to time.  
Edmund D. Gorski, President, CodePoets, Inc.
Success stories

PurchaseOptions


US Toll Free
877–634–0165
Outside US
+44–2035146725
Get your printable quote
Buy online starting from $249

Test Lint: Find common problems in your unit test code

Test Lint is now part of Isolator .NET and Test Lint Pro is part of Isolator .NET Server

Download Isolator .NET

We believe in unit testing and test driven development, and we also know how hard it is to learn to write proper unit tests that are readable, maintainable and trustworthy. That’s why we created Test Lint – the world’s first and only fully extensible coding advisor for unit tests in Visual Studio 2010.

What does it do?

Test Lint parses your code as you type it, and looks for common problems in your unit test code – from missing asserts to having tests depend on other tests – Test Lint will notify you on the spot about each possible issue with a visible queue right inside your editor, right next to the link where the issue appears.

Test Lint is Fully Extensible - you can create your own rules for it.

The Art of (Good) Unit Testing

Writing unit tests is easy. Writing good unit tests – that are readable, maintainable and trust-worthy is a bit harder if you’ve never done it before. So we took Roy Osherove (author of The Art of Unit Testing) and asked him to write down, based on his massive experience with unit testing, common problems that people do when they first start unit testing. Then we put that knowledge inside a Visual Studio 2010 extension– it’s like having your own personal coach letting you know of problems as you type them, really.

What issues does it detect?

Currently Test Lint finds a set of common problems:
  • Missing asserts in your tests
  • Multiple asserts \verifications on different objects in the same test
  • Tests that invoke other test methods
  • Logic inside unit tests (loops, Ifs Switchs..)

More rules will be added soon, and in upcoming versions, you will even be able to write your own rules based on our parsing infrastructure.

Works with all major frameworks

Test Lint will detect issues in tests written with:
  • Microsoft Test Framework
  • NUnit
  • MbUnit
  • XUnit.NET
  • CsUnit

Works with all major frameworks

Getting Started
  • Download the latest installation package (in vs 2010 package form)
  • Double click on the package to install into visual studio 2010 (RC and upwards)
  • If Vs 2010 is already running, you should restart it
  • Now that it’s installed and running, just open existing tests code, or start writing new test code.

Test Lint Pro: Test Lint Command Line Runner

Test Lint Pro (part of Isolator.NET Server) can run Typemock Test Lint as part of your automated build system, across your entire source code repository at one go!

  • Check all the tests in a specific solution, instead of working on a single file (like the Test Lint Addin)
  • Run Test Lint even on source code for projects in visual studio 2008 and 2005 (the Test Lint Addin only supports VS 2010 currently)
  • TeamCity output integration – you can see Test Lint Status inside TeamCity's build status page
  • Gives specific code location, including surrounding code lines, for each issue found