Comments on: Testing with Joda Time http://www.markhneedham.com/blog/2008/09/24/testing-with-joda-time/ Thoughts on Software Development Thu, 18 Mar 2010 23:35:30 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Test Doubles: My current approach at Mark Needham http://www.markhneedham.com/blog/2008/09/24/testing-with-joda-time/comment-page-1/#comment-20082 Test Doubles: My current approach at Mark Needham Tue, 14 Jul 2009 03:27:33 +0000 http://www.markhneedham.com/blog/?p=371#comment-20082 [...] that one situation where it would make more sense to use a hand written stub is when stubbing out a clock/time provider. This is because there are likely to be multiple calls to it all over the place and most of the [...] [...] that one situation where it would make more sense to use a hand written stub is when stubbing out a clock/time provider. This is because there are likely to be multiple calls to it all over the place and most of the [...]

]]> By: Bill Comer http://www.markhneedham.com/blog/2008/09/24/testing-with-joda-time/comment-page-1/#comment-19801 Bill Comer Wed, 08 Jul 2009 09:03:04 +0000 http://www.markhneedham.com/blog/?p=371#comment-19801 Excellent - very useful. Lots of other useful classes like LocalDate. Excellent – very useful.
Lots of other useful classes like LocalDate.

]]> By: Always use the front door « Stefan Roock http://www.markhneedham.com/blog/2008/09/24/testing-with-joda-time/comment-page-1/#comment-10608 Always use the front door « Stefan Roock Mon, 23 Feb 2009 19:42:57 +0000 http://www.markhneedham.com/blog/?p=371#comment-10608 [...] um deterministische Tests zu bekommen. Bei Unittests ist klar, dass man sich dafür einen Zeitgeber baut mit einem passenden Interface. So kann man den Zeitgeber dann mocken und hat damit volle [...] [...] um deterministische Tests zu bekommen. Bei Unittests ist klar, dass man sich dafür einen Zeitgeber baut mit einem passenden Interface. So kann man den Zeitgeber dann mocken und hat damit volle [...]

]]> By: Chris Burnley http://www.markhneedham.com/blog/2008/09/24/testing-with-joda-time/comment-page-1/#comment-1211 Chris Burnley Sun, 09 Nov 2008 22:13:10 +0000 http://www.markhneedham.com/blog/?p=371#comment-1211 Hey Mark, this looks familiar ;) Hey Mark, this looks familiar ;)

]]> By: Darren http://www.markhneedham.com/blog/2008/09/24/testing-with-joda-time/comment-page-1/#comment-455 Darren Wed, 24 Sep 2008 11:52:02 +0000 http://www.markhneedham.com/blog/?p=371#comment-455 Er, you know what most folks like to call their TimeProviders? Clock! SystemClock, MockClock etc. :) Joda has far more amounts of awesome than the java calendar/date horribleness. I have also found much benefit in going even further and wrapping third party classes in system specific implementations. It is a tough call to make but having all your dependencies abstracted away at the boundaries can be really useful, particularly with respect to (cough) well-understood concepts like time and money. A Business Day is a surprisingly slippery thing to get hold of and has only the loosest relationship to what the actual date is. Er, you know what most folks like to call their TimeProviders?

Clock!

SystemClock, MockClock etc. :)

Joda has far more amounts of awesome than the java calendar/date horribleness.

I have also found much benefit in going even further and wrapping third party classes in system specific implementations. It is a tough call to make but having all your dependencies abstracted away at the boundaries can be really useful, particularly with respect to (cough) well-understood concepts like time and money. A Business Day is a surprisingly slippery thing to get hold of and has only the loosest relationship to what the actual date is.

]]>