You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2016/10/19 01:55:59 UTC
[jira] [Updated] (APEXMALHAR-2306) Tests should allow for additions
to OperatorContext interface
[ https://issues.apache.org/jira/browse/APEXMALHAR-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Weise updated APEXMALHAR-2306:
-------------------------------------
Summary: Tests should allow for additions to OperatorContext interface (was: malhar unit test(s) have a dependency on OperatorContext in apex-core)
> Tests should allow for additions to OperatorContext interface
> -------------------------------------------------------------
>
> 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)