February 2011

Typemock News
Follow us:    
In This Issue

The Cost of a Single Bug
December's Skype outage cost millions of dollars in damage to the global economy and annoyed millions more, who were unable to conduct business, or connect with their friends and family.

Typemock's own Gil Zilberfeld posted about the Skype outage on his blog. According to Skype's CIO, a bug in an older version of the Windows Skype client was at the root of the service's failure. One little bug caused so much damage. The outage was covered worldwide.

Frequently, we hear "what's the ROI of testing?" Well, for Skype, it was millions in lost business, as well as significant negative media attention. 

As Gil wrote, "Could this bug have been prevented? Maybe. With proper practices, like code review, unit tests, acceptance tests — it may have been found before."
The Real ROI for Typemock Isolator
Why should a company use Typemock Isolator (besides it being an amazing tool for easy unit testing)? That question ultimately boils down to the business case: What is the actual ROI? How will Isolator save your company money?

One of our long-time customers recently wrote about how Typemock helped improve his productivity, saving him money. "Typemock is technically superior," he wrote. "By having the control that Typemock gives us, I could also write more 
thorough tests to cover a lot of the variability that our current product will likely encounter when in production. I also estimate that it would have saved me about 5 hours (~80% time savings) today alone, and also given us a near 100% coverage result."

So what's the business gain for this one customer?
  • Raise code coverage from 63% to near 100%
  • Less code to maintain
  • Time savings of 80% in one day
  • Ability to simulate any situation that can occur by mocking any scenario without touching source code

Our customers really are our best spokespeople.
Six Tips for Turbocharging Isolator
Who doesn't love making software run even better? Turbocharging, if you will. Here are Typemock developer's six tips for turbocharging Isolator.
  • Need to simulate a fault? Just use Isolate.WhenCalled(...).WillThrow(new Exception()) with any method!
  • Isolate.WhenCalled(...) uses Behavior Sequencing - use multiple expectations in sequence
  • Isolate.Swap.AllInstances() affects both existing and future instances of T!
  • Use Isolator to fake any Singleton without changing a line of code: Isolate.WhenCalled(() => MyFactory.Instance).WillReturn(...)
  • Use Isolate.WhenCalled(() => ...).CallOriginal() to have the fake object call an original implementation!
  • Use different flavors of argument matching when setting expectations: exact or custom

What are your favorite tips with Isolator or Isolator++? Send them to us or post them online and send us a link and we'll publish them in the next newsletter!
Congratulations to User Group Contest Participants

To show our support for the developer community, Typemock held a contest for user groups worldwide with lots of great prizes. Congratulations to our grand prize winner, MIGANG, the Great Lakes Area .NET User Group. 

Congratulations to all of the participants.

If you want Typemock or a Typemock evangelist to speak to your user group,please let us know. If you are interested in speaking about Typemock to your user group, please be in touch.
Among our customers:

Copyright © Typemock
If you were forwarded this email and would like to receive Typemock email promotions directly, pleaseclick here to subscribe.
If you would no longer like to receive future Typemock Offers and Updates, Click here to unsubscribe

USA TOLL FREE: # 877-634-0165 International: +972-3-6815177