You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Boris Shulman (JIRA)" <ji...@apache.org> on 2016/08/26 22:10:20 UTC
[jira] [Closed] (REEF-1533) Make RuntimeClock more testable and
create unit tests to check graceful and forceful shutdown of RuntimeClock
[ https://issues.apache.org/jira/browse/REEF-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shulman closed REEF-1533.
-------------------------------
Resolution: Fixed
> Make RuntimeClock more testable and create unit tests to check graceful and forceful shutdown of RuntimeClock
> -------------------------------------------------------------------------------------------------------------
>
> Key: REEF-1533
> URL: https://issues.apache.org/jira/browse/REEF-1533
> Project: REEF
> Issue Type: Test
> Components: REEF-Common, REEF-Tests
> Reporter: Sergiy Matusevych
> Assignee: Sergiy Matusevych
> Labels: test, unit-test, unit-test-missing
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)