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
866–895–4680
Outside US
+44–203–150–0293
Get your printable quote
Buy online

 

Don't depend on other tests

Having your unit test depend on another test can be a big annoyance down the line for your project. 

Types of test dependencies can be:

 

 

What problems can this cause?

 

 

What can I do to solve this?

usually people resort to this problem when they want to reuse code from the test that is being called (setting up some state in the system, for example). Instead of calling the other test, extract the common code that you want both tests to execute, into a utility method in your test class. then have both tests call that utility method.