Update Clock Tests

The recent update to the Clock component broke three unit tests (the
tests were actually checking for the incorrect behavior). This change
updates the tests to check for the correct behavior.

Change-Id: I8fafefeb5a673104c8446c9421b8a0bb98f46553
parent edaebb9e
......@@ -48,7 +48,7 @@ public class ClockTest extends TestCase {
}
public void testMakeInstantFromMillis() throws Exception {
assertEquals("Jan 1, 1970 00:00:00 AM",
assertEquals("Jan 1, 1970 12:00:00 AM",
Clock.FormatDateTime(Clock.MakeInstantFromMillis(0
- TimeZone.getDefault().getRawOffset()),""));
}
......@@ -75,12 +75,12 @@ public class ClockTest extends TestCase {
}
public void testAddWeeks() throws Exception {
assertEquals("Sep 10, 2002 00:00:00 AM", Clock.FormatDateTime(
assertEquals("Sep 10, 2002 12:00:00 AM", Clock.FormatDateTime(
Clock.AddWeeks(Clock.MakeInstant("9/11/2001 00:00:00"), 52), ""));
}
public void testAddWeeks2() throws Exception {
assertEquals("Sep 18, 2001 00:00:00 AM", Clock.FormatDateTime(
assertEquals("Sep 18, 2001 12:00:00 AM", Clock.FormatDateTime(
Clock.AddWeeks(Clock.MakeInstant("9/11/2001 00:00:00"), 1), ""));
}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment