Channels ▼


Unit Test Nirvana: Instant, Relevant & Before Integration Tests

Unit testing company Typemock has launched its Isolator V7 "instant" bug-testing tool for .NET developers. The product analyzes relevant units tests at any point in time skipping the longer integration tests so that bugs are identified as fast as possible.

Isolator V7 pinpoints the location of a bug in a developer's code based on the failed unit tests it carries out. It then offers guidance on how to repair it, showing the developer all the relevant unit tests for the method in hand. Tel-Aviv based Typemock says that unit testing is a proven methodology to help prevent bugs in production systems and that Isolator V7 enables programmers to develop code more efficiently by enabling them to identify bugs during the early stages of development.

Version 7 of this tool introduces "productivity booster" features that Typemock developed for internal usage, such as the Autorunner, automatic bug location with the Failed-Test Analyzer, and Visual Code Coverage.

  • The Autorunner runs only the relevant unit tests after every build providing feedback to the developer when a new bug is introduced.
  • The Failed-Test Analyzer points the developer to the exact location of the bug in the code by analyzing the failed unit tests.
  • Visual Coverage allows developers to know what code is covered by unit tests, so a developer will no longer test only the "if" statement and forget the "else" statement. Isolator V7 also lowers time-to-market by enabling companies to find and fix bugs quicker.

Typemock CEO Eli Lopian speaks of the dogfooding process his company has been through in the development of this product, saying that Isolator V7 enables them to release quicker because they are able to fix bugs faster. "At last, we are no longer slaves to our code. Seeing the code base covered with shields encourages developers to write more unit tests. It's fun and it finds our bugs for us," he said.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.