Interested in a
Personal Demo ?

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


 "Typemock has been really wonderful for us, it gave us strong tools to mock code in our tests project. With Support team, everything have been working really good, support team is really quick answering questions."
Daniel Veintimilla Tenorio, Software Engineer at Dexon Software
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.