Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Fri, 22 Aug 2014 20:36:11 +0000 (UTC)
From: "Alex Newman (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12736164.1408739678027.15995.1408739771364@arcas>
In-Reply-To: <JIRA.12736164.1408739678027@arcas>
References: <JIRA.12736164.1408739678027@arcas>
Subject: [jira] [Created] (HBASE-11806) Reasses test categories
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Alex Newman created HBASE-11806:
-----------------------------------

             Summary: 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)