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

Thomas Weise commented on APEXMALHAR-2306:
------------------------------------------

Have a look at FSInputModuleTest, for example.

Since the tests that use the test context were written with constructor 
dependency, it will be more work than just changing a factory method, but looks 
straightforward.

> malhar unit test(s) have a dependency on OperatorContext in apex-core
> ---------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2306
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2306
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>          Components: test benches
>            Reporter: Sanjay M Pujare
>
> While trying to build/test malhar against the latest apex-core, the following 
> failure was noticed
> .../apex-malhar/library/src/test/java/com/datatorrent/lib/helper/OperatorContextTestHelper.java:[47,17]
>  com.datatorrent.lib.helper.OperatorContextTestHelper.TestIdOperatorContext 
> is not abstract and does not override abstract method getName() in 
> com.datatorrent.api.Context.OperatorContext
> Ideally, malhar should mock up the OperatorContext interface or we should 
> find other ways to eliminate this kind of dependency.



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

Reply via email to