Telerik blogs

Tag: Mocking

  • Release

    JustMock is Getting a Facelift

    With the Q1 2015 release JustMock continues to evolve. It comes with a few exciting new features: Mocking Containers Integration (MEF or Unity for dependency injection) Entity Framework (EF) integration Improved Integration with TFS 2013 and TFS 2012 Download the latest version to try out the new features or read more about them on the What’s New page. We also wanted to make the mocking API cleaner. To make that possible, a few important changes will follow.
    Stefan Dragnev is a Principal Software Engineer at Telerik by Stefan Dragnev
    March 17, 2015
  • Release

    JustMock Lite Just Got Even Better

    We are open sourcing JustMock Lite and giving it to the community. We are giving you the chance to see and improve upon the JustMock Lite source code and share your changes with others. Now you can easily add any functionality that you need and want. We are sure you can make JustMock Lite even better.
    Todor-Totev by Todor Totev
    March 25, 2014
  • Productivity Testing

    30 Days of TDD – Day 23 – Mocking… FROM THE FUTURE!

    The examples I’ve been working with for this series have assumed that you are doing "Green Field” development. This means that we are writing an application from scratch and can make sure all of the things that make code testable are incorporated into our design from the start. The biggest one of these things being the user of dependency injection. But what if you are working on “legacy” code that still uses static dependencies and not dependency injection? Is TDD and unit testing out of reach due to a decision made at the beginning of the project? Not necessarily.
    by James Bender
    November 20, 2013
  • Productivity Testing

    Announcing the 2013 Q3 JustMock Release–Bigger and Badder Than Ever

    Check out all of the cool new features in JustMock 2013 Q3!
    Japikse by Phil Japikse
    October 18, 2013
  • Productivity Testing

    30 Days of TDD – Day 11 – What’s the Deal with “Mocking?”

    A goal of well written unit tests is to keep your test isolated. This means that even if your code under test relies on or is dependent on another class or external service you should be able to write your tests to exclude these dependencies and test only what’s in your current class or method. Sound impossible? It’s not, in fact if you’ve read my previous posts on Dependency Injection you already know half the answer to this problem. The other half of the solution is mocking.
    by James Bender
    October 02, 2013
Prev
1 2 3 4 5 6 7 8 9 10 ...
Next