[
https://issues.apache.org/jira/browse/HBASE-11806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107452#comment-14107452
]
Alex Newman commented on HBASE-11806:
-------------------------------------
I realized there's something wrong about my set setup please ignore the above
comment. Just because you pass -P run<test>Test doesn't guarantee that it's
only going to run those.
> Reasses test categories
> -----------------------
>
> Key: HBASE-11806
> URL: https://issues.apache.org/jira/browse/HBASE-11806
> Project: HBase
> Issue Type: Bug
> Reporter: Alex Newman
>
> HBase has an impressive set of tests. It remains a great investment and we
> have done a lot to make them comprehensive. However I feel like we could use
> some improvements on test categorization.
> From http://hbase.apache.org/book/hbase.tests.html
> "18.8.2.1. Small Tests
> Small tests are executed in a shared JVM. We put in this category all the
> tests that can be executed quickly in a shared JVM. The maximum execution
> time for a small test is 15 seconds, and small tests should not use a
> (mini)cluster.
> 18.8.2.2. Medium Tests
> Medium tests represent tests that must be executed before proposing a patch.
> They are designed to run in less than 30 minutes altogether, and are quite
> stable in their results. They are designed to last less than 50 seconds
> individually. They can use a cluster, and each of them is executed in a
> separate JVM.
> 18.8.2.3. Large Tests
> Large tests are everything else. They are typically large-scale tests,
> regression tests for specific bugs, timeout tests, performance tests. They
> are executed before a commit on the pre-integration machines. They can be run
> on the developer machine as well."
--
This message was sent by Atlassian JIRA
(v6.2#6252)
