[
https://issues.apache.org/jira/browse/PHOENIX-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926402#comment-13926402
]
James Taylor commented on PHOENIX-130:
--------------------------------------
Another option would be to match the tests based on the package name being
end2end. We consistently name our tests this way. Then we wouldn't have to move
them all around.
> 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)
