nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-1685) Optimize database Junit tests to reduce execution time.
Date Sun, 17 Apr 2016 00:34:25 GMT

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

ASF subversion and git services commented on NIFI-1685:
-------------------------------------------------------

Commit 65c18b6ef55fe3fcfa34803f8a327a8432838e37 in nifi's branch refs/heads/0.x from [~Toivo
Adams]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=65c18b6 ]

NIFI-1685 Optimize database Junit tests to reduce execution time.  Removed commented blocks.

This closes #304.

Signed-off-by: Joe Skora <jskora@apache.org>


> Optimize database Junit tests to reduce execution time.
> -------------------------------------------------------
>
>                 Key: NIFI-1685
>                 URL: https://issues.apache.org/jira/browse/NIFI-1685
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Tools and Build
>            Reporter: Toivo Adams
>            Assignee: Toivo Adams
>            Priority: Minor
>              Labels: build, test
>
> Some database Junit tests are slow.
> For example:
> Running org.apache.nifi.processors.standard.TestPutSQL
> Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 116.638 sec - in org.apache.nifi.processors.standard.TestPutSQL
> Running org.apache.nifi.processors.standard.util.TestJdbcCommon
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.029 sec - in org.apache.nifi.processors.standard.util.TestJdbcCommon
> Running org.apache.nifi.processors.standard.TestExecuteSQL
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.978 sec - in org.apache.nifi.processors.standard.TestExecuteSQL
> Running org.apache.nifi.processors.standard.util.TestJdbcHugeStream
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.253 sec - in org.apache.nifi.processors.standard.util.TestJdbcHugeStream
> Running org.apache.nifi.processors.standard.QueryDatabaseTableTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.544 sec - in org.apache.nifi.processors.standard.QueryDatabaseTableTest
> My dev machine is not the fastest one, but still why waste time.
> One of reasons is creating DBCPService for each test.
> Setting up Connection pooling is expensive operation.
> So DBCPService should be set up only once and reuse in each test.
> Thanks
> Toivo



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

Mime
View raw message