Search The Blog
Latest Posts
from 5whys.com
Twitter: @RoyOsherove
About this site

TDD in .NET Online Course

TDD and BDD in Ruby Online Course

 

Subscribe!

This site aims to connect all the dots of my online activities - from tools, books blogs and twitter accounts, to upcoming conferences, engagements and user group talks.

« Join me for a live webinar on unit testing with Isolator++ this thursday | Main | Announcing Isolator++, and closing a TDD circle »
Thursday
Oct142010

What’s coming in Test Lint 1.5

Test Lint is an “as you type” parser that detects common readability, maintainability and trust anti-patterns in your unit tests. the addin for VS is free. there is also a command line version that you can use in your automated builds.

Here’s a sneak preview of things to come in Test Lint next month (here are the still unfinished new docs):

  • we added 3 categories for rules – Trust, Readability, and Maintainability

We’ve added 10 new rules to Test Lint, that detect more “advanced” yet common problematic scenarios:

New Trust Related Issues:

  • Avoid hand rolled mocks or stubs that contain custom logic (hard coded values or pure logic)
  • We’ll try to detect when you put production logic in your unit test, and give you a hint about it
  • We’ll help make sure you separate unit from integration tests, by detecting integration tests in a project that doesn’t have the word “integration” at its subject.
  • Avoid Random Generation in tests: your test will keep changing on every run.

new Readability Rules:

  • Avoid confusing mocks and stub variable names
  • Don’t create fakes in setup methods

New Maintainability rules

  • Prefer factory method to create objects under test
  • Avoid over specification in test (calling verifyAll on mocks)

New Isolator Specific Rule

  • Avoid calling “new” inside “whencalled” calls

PrintView Printer Friendly Version

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
Web Analytics