Absolutely. I'd respectfully suggest that this is more a requirement of the way the step definition or test fixture that implements the feature needs to behave than the intent of describing time based logic in a natural language such that product owners, ba's etc. can write them (i.e. Cucumber, FitNesse, etc). That Chronic takes into consideration the things you mention (time zone, DST, Leap Years, etc), is simply an imperative of it. Anyway, I think it fits hand-in-glve with Cucumber and BDD in general. Just for the record, I have no vested interest in Chronic and really don't know who even authored it, but I can say it's looking pretty awesome in our own Cucumber tests.
Thanks, Tim On Sun, Mar 1, 2009 at 4:30 PM, Mark Wilden <[email protected]> wrote: > On Sun, Mar 1, 2009 at 11:07 AM, Mark Wilden <[email protected]> wrote: >> >> Just be careful when when basing durations from "now" that daylight >> savings time doesn't affect anything. > > Along the same lines, don't write tests that assume 1.month.ago was < > 29 days ago, or specs could start failing in March (as just happened > with us). :) > > ///ark > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
