[REEF-1533] Make RuntimeClock more testable and create unit tests to check graceful and forceful shutdown of RuntimeClock

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: REEF-Common, REEF-Tests
• Labels: test unit-test unit-test-missing
• Assignee: Sergiy Matusevych
• Reporter: Sergiy Matusevych
• Created: 18/Aug/16 18:26
• Updated: 12/Sep/16 19:57
• Resolved: 26/Aug/16 22:10

Description

Current version of the RuntimeClock does not have unit tests to verify correctness of graceful .close() and forceful .stop() shutdown of the event loop. We need to add such tests to ClockTest.
Also, Clock and RuntimeClock are not good for testing - e.g. we cannot check if the clock is indeed in the closed state, or check what exact time the alarm had been scheduled for. Shutdown tests may require such changes in the Clock interface.

Issue Links

• requires: REEF-1527 Graceful shutdown of the RuntimeClock is not so graceful: unconditionally clears the event queue