Basically also in our bank such discussions were initiated. Basically, when testing integrated systems this is a very functional way to simulate different time scenarios, eg year end processing.
For testing smaller libraries i personally prefer to dynamically provide test data or services/mocks for the corresponding tests. This, contrary to the global solution, still allows isolation of my test cases/suites...
Tel +41 (43) 317 05 30
Send from Mobile
Am 17.07.2013 um 19:47 schrieb Werner Keil <werner.keil@... <mailto:werner.keil@...>>:
This pattern for testing timestamps might be useful, too: http://www.javapractices.com/topic/TopicAction.do?Id=234
While it (obviously) uses long, such a layer could also allow using multiple Date/Time APIs behind the scenes, and come handy for either simple unit tests or maybe those in the TCK, too.
Since most parts of the API tend to consume a timestamp, using such an interface as part of the actual API may not help much, there, or does anybody feel it would benefit?
|Tresch Anatole (KFSC 225)||07/18/2013|
[JSR-354] Re: JSR 354 API Update