Interested in a
Personal Demo ?

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


"I find a new use for Typemock each time I use it... It's not often a product fills a gap so well… I was impressed. It takes care of a big hole in unit testing"
John Spano, CTO and Co-Founder, NeoTekSystems
Success stories


US Toll Free
Outside US
Get your printable quote
Buy online


Switched 'Actual' and 'Expected' parameters in a call to Assert.AreEqual(expected,actual)


This is a very common mistake. If you make this mistake, the errors that appear in the error message of the assert can be misleading and make it harder to understand what the bug is.

Make sure to use the 'expected' value as the first parameter in the assert call.