[
https://issues.apache.org/jira/browse/PHOENIX-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930057#comment-13930057
]
James Taylor commented on PHOENIX-130:
--------------------------------------
One other thought here, that is a plus for relocating the test, is that they
can easily be run in bulk in Eclipse which is pretty handy. Especially running
all the non end2end tests, as they complete quickly and give you some idea if
you've broken anything almost immediately.
FYI, we're wrapping things up for 3.0/4.0 this week. We need to cut an RC this
Monday at the latest. Not a huge deal, as anything that doesn't make it can be
put in a 3.1/4.1 release.
> Separate execution of slow (integration) tests from fast unit tests
> -------------------------------------------------------------------
>
> Key: PHOENIX-130
> URL: https://issues.apache.org/jira/browse/PHOENIX-130
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Gabriel Reid
> Attachments: PHOENIX-130.patch
>
>
> The current collection of automated unit tests and integration tests takes a
> significant amount of time to run (somewhere in the neighborhood of 90
> minutes on my machine).
> I’d like to propose that the automated tests are split up into two groups:
> * unit tests, which don’t make use of a running HBase and run quickly, and
> will be run within the maven test phase
> * integration tests, which do make use of a running HBase and run more
> slowly, and will be run within the maven integration-test phase
> This approach has the advantage that all fast-running unit tests will be run
> before the integration tests, so if there is a minor issue the build will
> fail-fast instead of first running long-running integration tests before
> failing. It also makes it possible to quickly and regularly run “mvn test”
> during development to run all unit tests in a matter of seconds.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
