flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-4434) Add a testing RPC service
Date Fri, 19 Aug 2016 21:39:21 GMT

     [ https://issues.apache.org/jira/browse/FLINK-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stephan Ewen updated FLINK-4434:
--------------------------------
    Description: 
I suggest to add a simple testing RPC service that allows to register mock gateways under
certain names.

That way, if a component connects to another component via the RPC service, it will call the
mock gateway, rather than the proper proxy gateway that will try to send actor messages.

Tests on mocks are very easy and powerful with tools like Mockito.

  was:
I suggest to add a simple testing RPC service that allows to register mock gateways under
certain names.

That way, if a component connects to another component via the RPC service, it will call the
mock gateway, rather than the proper procy gateway that will try to send actor messages.

Tests on mocks are very easy and powefull with tools like Mockito.


> Add a testing RPC service
> -------------------------
>
>                 Key: FLINK-4434
>                 URL: https://issues.apache.org/jira/browse/FLINK-4434
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Distributed Coordination
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 1.2.0
>
>
> I suggest to add a simple testing RPC service that allows to register mock gateways under
certain names.
> That way, if a component connects to another component via the RPC service, it will call
the mock gateway, rather than the proper proxy gateway that will try to send actor messages.
> Tests on mocks are very easy and powerful with tools like Mockito.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message