You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2017/10/11 08:05:02 UTC

[jira] [Commented] (REEF-1898) Add mocked REEF interfaces to improve unit testing of REEF applications

    [ https://issues.apache.org/jira/browse/REEF-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199939#comment-16199939 ] 

Markus Weimer commented on REEF-1898:
-------------------------------------

+1 on this idea. [~motus] made it so you can run the REEF Driver in the same process as the client. This makes it possible to step through the Driver in your IDE's debugger. Adding similar support for Tasks makes a lot of sense. We could resurrect the single-process runtime to make that happen.

> Add mocked REEF interfaces to improve unit testing of REEF applications
> -----------------------------------------------------------------------
>
>                 Key: REEF-1898
>                 URL: https://issues.apache.org/jira/browse/REEF-1898
>             Project: REEF
>          Issue Type: Test
>            Reporter: Sean Po
>            Priority: Minor
>
> Currently using REEF, applications can be tested without external setup by using the local runtime. However, this method gives no visibility into Task / Evaluator failures, and successes; the local runtime mocks out components on the Container level. In order to write tests with deeper coverage, a REEF layer needs to be mocked out with hooks provided to control Task / Evaluator flow.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)