Unit Testing Time and Dates is an often talked about problem with relatively simple solutions. More difficult is the acceptance/system testing with Time. What strategies are used?
Well-known agilist and TDD expert J.B. Rainsberger has begun a series of posts to explain why his experience has led him to the thought-provoking conclusion that "integration tests are a scam".
Version 3.0 RTM of the popular Moq .NET mocking library is now available. Moq 3.0 includes Silverlight support, improved event and property mocking, Pex integration, and improved samples.
Hot in the TDD Yahoo group is a discussion concerning the perceived continuum between the "Classic" and "Mockist" TDD. Steve Freeman, Nat Pryce, Michael Feathers, Dale Emery, and many more discuss terminology and describe their approaches. The discussion also debates whether there even really exists such a continuum, and if so, what distinguishes the approaches that represent it's extremes?
After open-sourcing their C++ Test Framework a few months ago, Google has just open-sourced the Google C++ Mocking Framework (Google Mock) under the BSD license.
Version 3.5 of the popular Rhino Mocks .NET mocking framework has been released. This version marks a major change in the API. A new 'Arrange, Act, Assert' syntax has been added as an alternative to the exiting 'Record-Replay' semantics. This syntax makes strong use of lambda expressions and extension methods, among other .NET 3.5 language enhancements.
The latest release of the Mockito mocking framework enables spying on non-mock objects and introduces a cleaner stubbing syntax.
Moq is a mocking library for .NET designed and developed to utilize .NET 3.5 features, e.g., Linq expression trees and lambda expressions. Moq's goal is to be simple and straightforward, allowing a natural integration into existing unit tests, instead of forcing developers to rewrite tests or learn extensive Record/Replay mocking frameworks.
In this presentation filmed during QCon London 2007, Nat Pryce and Steve Freeman talk about TDD using Mock Objects. In their opinion, Mock Objects improves the software design and makes the code more easier to maintain and adapt to changing requirements.
In his 'Ode To Code' K Scott Allen offers rational for the use of mock objects when unit testing and discusses his thoughts on the use of mock object frameworks.
Service simulation (mocking) – the ability to mimic service behavior even before they are implemented - enables service consumer developers and testers to parallelize their efforts without having to wait for service implementation to complete. Service simulation also provides a light-weight alternative to building expensive reference environments.
The ease of Ruby for scripting tasks makes it a very powerful candidate for writing your Test suites. Until recently there was no real standalone framework to test your Java with Ruby. JtestR, written by Ola Blini (a member of JRuby team) and Anda Abramovici, makes it possible now. Ruby coupled with powerful Ruby tools such as RSpec, mocha will make writing Java tests smoother.
There has been an interesting discussion in the blogosphere about the benefits or lack of benefits from using Dependency Injection. The question is — does Dependency Injection really pay off?
A new InfoQ article looks at evaluating performance in an iterative and continuous manner.
The latest version of the very popular mocking framework, Rhino Mocks version 3.3 is complete and ready to be used by your tests. This release provides many new features including Remoting Proxies and more.