Telerik blogs

Tag: Mocking

  • Productivity Testing

    Automocking with JustMock

    Auto mocking containers are designed to reduce the friction of keeping unit test beds in sync with the code being tested as systems are updated and evolve over time. Read how JustMock helps with automocking.
    Japikse by Phil Japikse
    March 11, 2013
  • Productivity Testing

    Handling Arguments in JustMock Arrangements

    Mocking is all about making it easy to isolate the system under test in unit tests. In non profiled mocking, this is typically done by creating a proxy for an interface, and arranging the methods that will be called on the proxy. Mocking frameworks like JustMock determine matching calls not only based on the method signature, but also by the values of the arguments passed into the method. JustMock provides many mechanism to tune how the matching is done.
    Japikse by Phil Japikse
    February 21, 2013
  • Productivity Testing

    KickStart Your .NET Mocking

    Getting started with mocking can be hard. In this article, I describe the path that I took on my way to becoming a frequent mocker.
    Japikse by Phil Japikse
    February 04, 2013
  • Productivity Testing

    Asserting Behavior with JustMock

    JustMock is a great tool for abstracting dependencies in unit tests, and the new automocking feature makes it even faster to develop unit tests.  Another great feature in JustMock and JustMock Lite is the capability to assert the behavior of your system under test.  Traditional TDD (Test Driven Testing) unit testing typically tests for state.  Did the user get logged in? Did the user’s shopping cart get loaded?  Important tests, of course.  But that only tests the end result of the method.  If the user does NOT successfully login, and the cart is not reloaded, is that because the call to the repository was never called? Or because some error happened that didn’t reload the cart in this particular use case?  The state of the application is correct, but is that because it executed the expected behavior, or because we got lucky? 
    Japikse by Phil Japikse
    January 10, 2013
  • Productivity

    Mocking Property Getters and Setters

    In typical unit testing scenarios, mocking property getters and setters isn't high on the list of areas of concern. Where it usually comes into play is when an entity’s properties’ values (or the act of setting them) are part of the scaffolding, or behavior for the system under test.
    Japikse by Phil Japikse
    December 27, 2012
Prev
... 11 12 13 14 15
Next