sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2013) What is the story for External Connectors to write unit and integration tests?
Date Thu, 15 Jan 2015 17:56:36 GMT

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

Jarek Jarcec Cecho commented on SQOOP-2013:
-------------------------------------------

Good point [~vybs]. I think that it's fine if internal connectors will share their test utilities
and expose them to connector developers. We should however careful mark those with the visibility
annotations that [~abec] is working on, to ensure that we have the distinction between what
is indeed meant to be used externally.

If an external connector want to share an utility, then I'm afraid that this will have to
be contributed to Sqoop as any other patch.

> 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
>            Assignee: 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)

Mime
View raw message