This project is read-only.

FAQ

Is NMock3 backward compatible with NMock2?

The version titled 'NMock3 - RC1, .NET 4.0' on the download page is completely backward compatible. In fact, you can mix syntax within your unit tests.

Why is the namespace NMock2 and the assembly named NMock3 of the download titled 'NMock3 - RC1, .NET 4.0'?

Typically version numbers are discouraged from being included in namespaces. We decided not to perpetuate the practice of including the version number 3 in the namespace and left it at 2. This maintains backward compatibility with all existing tests. The newest RTM versions are just NMock.

What does the version number mean?

The version number is read as Major.Minor.Build.Framework where "Framework" is the version of the .NET framework to which the assembly is compiled. 35 = .NET 3.5, 40 = .NET 4.0

Why another mocking framework (or the enhancement of an existing one)?

Several reasons:
  1. NMock has a history of being very easy to read and understand. If it is easy to understand, developers are more likely to adopt it.
  2. NMock doesn't rely on the record/replay requirements as other mocking frameworks do.
  3. NMock can set up event binding expectations. (Other frameworks, such as Moq, couldn't do this at the time I looked at them)
  4. NMock is now using lambdas which support code refactoring and compile-time checking!

Last edited Jul 27, 2011 at 6:12 PM by pwolfe, version 5

Comments

No comments yet.