You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Chris Westin (JIRA)" <ji...@apache.org> on 2015/04/22 20:44:58 UTC

[jira] [Updated] (DRILL-2026) Consider: speed up dev. tests using Maven "integration-test" phase

     [ https://issues.apache.org/jira/browse/DRILL-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Westin updated DRILL-2026:
--------------------------------
    Fix Version/s:     (was: 1.0.0)
                   1.1.0

> Consider: speed up dev. tests using Maven "integration-test" phase
> ------------------------------------------------------------------
>
>                 Key: DRILL-2026
>                 URL: https://issues.apache.org/jira/browse/DRILL-2026
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Tools, Build & Test
>            Reporter: Daniel Barclay (Drill)
>            Assignee: Steven Phillips
>             Fix For: 1.1.0
>
>
> Because many of our unit test classes (unit tests in the sense of being run by Surefire in Maven's "test" phase) need to have a running Drillbit, then because they are unit tests, each such test class starts up its own Drillbit, taking quite a while, especially considering the aggregate time.
> Consider moving Drillbit-needing tests to be Maven integration tests (run in Maven's "integration-test" phase by Failsafe).
> That would allow for starting up a Drillbit (or multiple Drillbits and other servers) in Maven's "pre-integration-test" phase, using those servers for all tests, and shutting down the servers in Maven's "post-integration-test" phase.
> That should save quite a lot of time--the product of the time per Drillbit startup plus shutdown and the number of test classes changed to integration tests.



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