Some minor issues: the comment is misleading, date under test is 30/03/2014 (months are 0-based in JS). Also in general I don't like providing error messages like "x should be 7" (but not telling what it is instead). Hint: you can use sth like `"30/03/2014 02:15:00 UTC should be formatted to '%2' but got '%1'"` (see #327).

--

That's an interesting edge case. Checked locally and it seems to happen only during the time corresponding to local DST change which means 1 hour window.

The issue is that this test is locale-dependent (the test is "red" before code change only on machines with western European timezone, and maybe some others, because 30/03/2014 02:15 local time doesn't exist). On some platforms this test will be green because they enable DST on another day, or another time (01:00 for instance).

Specifically, it will *always be green on Travis machines* because from what I've found they use UTC time - probably we can't do anything with that issue. But I guess we can live with it.