[
https://issues.apache.org/jira/browse/HBASE-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108322#comment-13108322
]
Jesse Yates commented on HBASE-4438:
------------------------------------
Been thinking about the issue of how we want to handle breaking out the
integration tests.
*Option 1*
we can have all the tests (integration and unit) in a single source folder
(hbase/src/test/java/*) which then uses standard conventions for naming to
ensure things are run correctly - ie at the right time
* Unit tests would remain in the standard format ( \*\*/\*Test.java,
\*\*/Test\*.java, **/*TestCase.java)
* integration tests would move to a similar format ( \*\*/\*IT.java,
\*\*/IT\*.java, **/*ITCase.java)
we can move integration tests to their own sub-module of hbase. This would be
a little more of a radical change.
> Speed the build test phase
> --------------------------
>
> Key: HBASE-4438
> URL: https://issues.apache.org/jira/browse/HBASE-4438
> Project: HBase
> Issue Type: Umbrella
> Components: test
> Reporter: stack
>
> We're up to 2hrs 15mins running tests on jenkins which is kinda crazy. Akash
> started a thread over in dev on fixing this:
> http://search-hadoop.com/m/cZjDH1ykGIA/Running+UnitTests+before+submitting+a+patch&subj=Running+UnitTests+before+submitting+a+patch
> Jessie brings up http://maven.apache.org/plugins/maven-failsafe-plugin/ which
> looks like something we need to start using; having a tiering of our testing
> would make sense to me.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
