Interested in a
Personal Demo ?

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


"Typemock has helped us get some difficult to test code under test, as well as speed up the writing of some business rules/classes. The new version is quite impressive with the suggested tests. Any tool that helps you write more (and better!) tests has got to help make better quality code." 
Stephen Price Lead Developer at Unlisted Marketplace
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.