[
https://issues.apache.org/jira/browse/SQOOP-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276030#comment-14276030
]
Jarek Jarcec Cecho commented on SQOOP-2013:
-------------------------------------------
Very good question [~vybs], providing external connectors ability to test the
connector is indeed super important. I was having this requirement in mind when
I started working on the {{test}} module and that is why there are so many
re-usable code - including the most important
{[{SqoopMiniCluster}}|https://github.com/apache/sqoop/blob/sqoop2/test/src/main/java/org/apache/sqoop/test/minicluster/SqoopMiniCluster.java]
that allows to start entire Sqoop server from within unit test. I'm pretty
sure that there will be rough edges until someone actually try to use it in
external connector, but yes, connector developers are expected to reuse those
pieces.
> 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)
