[JSR-354] Re: JSR 354 API Update
- From: Anatole Tresch <atsticks@...>
- To: "jcurrency_mail@..." <jcurrency_mail@...>
- Subject: [JSR-354] Re: JSR 354 API Update
- Date: Wed, 17 Jul 2013 21:15:30 +0200
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@...>:
> This pattern for testing timestamps might be useful, too:
> 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?