Link Details

Link 999695 thumbnail
User 418158 avatar

By daniel.marbach
via planetgeek.ch
Published: Jul 18 2013 / 08:24

In most of the projects in our company we used the mocking framework Moq. Nowadays we are moving away from Moq to FakeItEasy because FakeItEasy is just faking amazing! Seriously, FakeItEasy provides us a cleaner and more readable syntax. It just has the concept of fakes, no need to call .Object everywhere and many more advantages. Our rule of thumb is that we simply apply the boy-scout rule for the migration process from Moq to FakeItEasy. This means if a developers touches a unit test, which contains Moq Mocks, then he quickly rewrites it to FakeItEasy. But doing that manually is tedious and error prone. Why not use Resharper’s powerful search and replace patterns to rewrite our tests almost automatically? Indeed this can be done and I’ll show you how you achieve it with Resharper.
  • 5
  • 0
  • 456
  • 300

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (5)



Voters Against This Link (0)



    Java Performance Optimization
    Written by: Pierre-Hugues Charbonneau
    Featured Refcardz: Top Refcardz:
    1. Design Patterns
    2. OO JS
    3. Cont. Delivery
    4. Java EE7
    5. HTML5 Mobile
    1. Node.js
    2. Debugging JavaScript
    3. OO JS
    4. JSON
    5. Ajax