Microsoft Fakes and .Net 4.0

We studied the use of the new Fakes framework to help us increase our testing coverage with some legacy .NET code. framework Unfortunately, it seems that we will not be able to upgrade to .net 4.5. Should I correctly say that we cannot use the framework with .net 4.0 (and VS2012) and that we will need to use the now unsupported Moles structure instead?

+5
source share
5 answers

Although I'm not a fan of moles in general, I understand how much help they can get when testing outdated code. Below are some other tools you may consider. But seriously, I hate these types of frameworks because the right way to do this is to write code that can be tested and use outdated refactoring code that is not (I understand that this is not always easy or possible). I think moles get rid of one of the main advantages of unit testing, and this is that it makes you write good code, as described here:

Here are a few things to consider:

  • Moles (Predecssor to MS Fakes Framework)
  • JustMock (Less expensive than TypeMock but still expensive)
  • TypeMock ( !)

, JustMock, , .

+4

Visual Studio 2012 Ultimate Premium Update 2, Microsoft Fakes, .NET framework.

+2

, , , / , Microsoft Microsoft?

Rhino.Mocks , FakeItEasy . , .

0

3.5 , 4.5. 3.5, .

0

Microsoft Fakes supports the same .NET versions as Visual Studio 2012 itself. This includes versions 4.5, 4.0, 3.5, 3.0, and 2.0.

0
source

All Articles