drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Altekruse (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-2026) Consider: speed up dev. tests using Maven "integration-test" phase
Date Wed, 19 Aug 2015 21:10:46 GMT

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

Jason Altekruse updated DRILL-2026:
-----------------------------------
    Fix Version/s:     (was: Future)
                   1.2.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: Jason Altekruse
>             Fix For: 1.2.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)

Mime
View raw message