Interested in a
Personal Demo ?


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

Testimonials


"I thank the heavens for Typemock. This is E.X.A.C.T.L.Y what I have been looking for. Thank you so much guys."
Michael Nyika, Fool.com
Success stories

PurchaseOptions


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

The following article appeared in Sys-Con on May 24, 2011

The Difference Between Unit Testing and Integration Testing

This article will discuss how to prevent your unit tests turning into integration tests. 

By Gil Zilberfeld

First things first:

What is a unit test?

A unit test is:

By breaking any of these guidelines, you increase the chance of developers either not trusting or not believing the test results (due to repeated false failures by the tests), or people not wanting to run the tests at all because they run too slowly.

What is an integration test?
An integration test is any test that can't be described as a unit test. The different kinds of integration tests (performance tests, system tests, acceptance tests etc.) are not the subject of this piece. Our main concern here is just differentiating unit tests from everything else.

An integration test might:

Taking those bullets into account, we can say that Integration tests will most likely:

When do integration tests make sense?
Integration tests can make a lot of sense in most systems in two particular configurations:

Additional regression test layer
Integration tests can serve as an extra "smoke test" that can be run when the full system needs to be tested, proving that deployment of all the system components works well, for example. With those kinds of tests, you would test many small things in one large test case.

Integration tests on legacy code
Michael Feathers, in his book "Working Effectively with Legacy Code" defined legacy code as "code that does not have tests." It's usually hard or impossible to write unit tests for such code, as it is mostly untestable. Tools like Typemock Isolator help relieve that problem by being able to fake anything, and integration tests can serve as an additional smoke test to make sure you didn't break the integration between system components, one level above unit tests.

Summary
By being able to distinguish unit from non-unit tests, we can make sure they are separated in our projects, and give our developers a "safe green zone" (as mentioned in Roy Osherove's book ‘The Art of Unit Testing') that contains only unit tests, in which developers can run and always trust the results.

•   •   •

With over 15 years of experience in software development, Gil has worked with a range of aspects of software development, from coding to team management, and implementation of processes. Gil presents, blogs and talks about unit testing, and encourages developers from beginners to experienced, to implement unit testing as a core practice in their projects. Gil writes a personal blog (http://www.gilzilberfeld.com), and contributes to the Typemock blog - http://blog.typemock.com/