[
https://issues.apache.org/jira/browse/SQOOP-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276039#comment-14276039
]
Veena Basavaraj commented on SQOOP-2013:
----------------------------------------
First of all, the test module is super useful. Great!
But one additional thing that may happen is this, there might be custom
utilities that a connector may want to add so that other connectors can test
against it for the FROM/ TO
For instance if you see kafka connector that we added internally
public class KafkaConsumer
public class KafkaLocal
public class TestUtil {
all this custom code was added to common-test, since we have access to this
code base, we did that, So how would a external connector expose such utilities
?
> What is the story for External Connectors to write unit and integration tests?
> ------------------------------------------------------------------------------
>
> Key: SQOOP-2013
> URL: https://issues.apache.org/jira/browse/SQOOP-2013
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Fix For: 1.99.5
>
>
> As simple as it sounds, today for any external connector to test itself we do
> not provide good means to do that.
> where do we expect the integration tests to reside for new connectors?
> how can they use the JDBC connector test utilies ? or HDFS test utilties?
> is the recommended approach to depend on the test module?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
