New tool discovery: Testability Explorer

[Mark Levison-2]

I just stumbled across the Testability Explorer
<http://code.google.com/p/testability-explorer/>and I'm immediately left
wondering why haven't I heard of this before? It sounds like an excellent
tool, especially for assessing a project that wasn't developed using TDD.

Has any one used it? Does it live up to the promises made:
http://misko.hevery.com/2008/10/21/testability-explorer-measuring-testability/

--
Cheers
Mark Levison
Blog: http://www.notesfromatooluser.com/
Recent Entries: Agile/Scrum Smells:
http://www.notesfromatooluser.com/2008/06/agilescrum-smells.html
Agile Games for Making Retrospectives Interesting:
http://www.notesfromatooluser.com/2008/10/agile-games-for-making-retrospectives-interesting.html


[Non-text portions of this message have been removed]

[Kaleb Pederson-2]

On Wed, Nov 5, 2008 at 12:57 PM, Mark Levison <mark@...> wrote:
> I just stumbled across the Testability Explorer
> <http://code.google.com/p/testability-explorer/>and I'm immediately left
> wondering why haven't I heard of this before? It sounds like an excellent
> tool, especially for assessing a project that wasn't developed using TDD.

I was looking at this just yesterday.

The idea of "Testable" cyclomatic complexity, or "Non-Mockable Total
Recursive Cyclomatic Complexity" as they state it,  makes perfect
sense -- if you can't mock a classes interactors, then they add to the
complexity of the class.

Similarly, if a class can access globals -- it's more complex because
it's behavior is harder for tests to guarantee, etc.

> Has any one used it? Does it live up to the promises made:
> http://misko.hevery.com/2008/10/21/testability-explorer-measuring-testability/

I haven't used it yet... but I've strongly considered running it
against a couple of legacy code projects that I have to work on once
in a while.... I just hope I won't get an INT overflow if I do ;).

--Kaleb