Package org.apache.hadoop.hbase.testclassification
package org.apache.hadoop.hbase.testclassification
-
ClassDescriptionorg.apache.hadoop.hbase.testclassification.ClientTestsTag a test as related to the client.org.apache.hadoop.hbase.testclassification.CoprocessorTestsTag a test as related to coprocessors.org.apache.hadoop.hbase.testclassification.FilterTestsTag a test as related to the
org.apache.hadoop.hbase.filter
package.org.apache.hadoop.hbase.testclassification.FlakeyTestsTag a test as failing commonly on public build infrastructure.org.apache.hadoop.hbase.testclassification.IntegrationTestsTag a test as 'integration/system' test, meaning that the test class has the following characteristics: Possibly takes hours to complete Can be run on a mini cluster or an actual cluster Can make changes to the given cluster (starting stopping daemons, etc) Should not be run in parallel of other integration tests Integration / System tests should have a class name starting with "IntegrationTest", and should be annotated with @Category(IntegrationTests.class).org.apache.hadoop.hbase.testclassification.IOTestsTag a test as related to theorg.apache.hadoop.hbase.io
package.org.apache.hadoop.hbase.testclassification.LargeTestsTagging a test as 'large', means that the test class has the following characteristics: it can executed in an isolated JVM (Tests can however be executed in different JVM on the same machine simultaneously so be careful two concurrent tests end up fighting over ports or other singular resources). ideally, the whole large test-suite/class, no matter how many or how few test methods it has, will run in last less than three minutes No large test can take longer than ten minutes; it will be killed.org.apache.hadoop.hbase.testclassification.MapReduceTestsTag a test as related to mapred or mapreduce.org.apache.hadoop.hbase.testclassification.MasterTestsTag a test as related to the master.org.apache.hadoop.hbase.testclassification.MediumTestsTagging a test as 'medium' means that the test class has the following characteristics: it can be executed in an isolated JVM (Tests can however be executed in different JVMs on the same machine simultaneously so be careful two concurrent tests end up fighting over ports or other singular resources). ideally, the whole medium test-suite/class, no matter how many or how few test methods it has, will complete in 50 seconds; otherwise make it a 'large' test. Use it for tests that cannot be tagged as 'small'.org.apache.hadoop.hbase.testclassification.MetricsTestsTag a test that covers our metrics handling.org.apache.hadoop.hbase.testclassification.MiscTestsTag a test as not easily falling into any of the below categories.org.apache.hadoop.hbase.testclassification.RegionServerTestsTag a test as related to the regionserver.org.apache.hadoop.hbase.testclassification.ReplicationTestsTag a test as related to replication.org.apache.hadoop.hbase.testclassification.RestTestsTag a test as related to the REST capability of HBase.org.apache.hadoop.hbase.testclassification.RPCTestsTag a test as related to RPC.org.apache.hadoop.hbase.testclassification.SecurityTestsTag a test as related to security.org.apache.hadoop.hbase.testclassification.SmallTestsTagging a test as 'small' means that the test class has the following characteristics: it can be run simultaneously with other small tests all in the same JVM ideally, the WHOLE implementing test-suite/class, no matter how many or how few test methods it has, should take less than 15 seconds to complete it does not use a clusterorg.apache.hadoop.hbase.testclassification.VerySlowMapReduceTestsTag a test as related to mapreduce and taking longer than 5 minutes to run on public build infrastructure.org.apache.hadoop.hbase.testclassification.VerySlowRegionServerTestsTag a test as region tests which takes longer than 5 minutes to run on public build infrastructure.org.apache.hadoop.hbase.testclassification.ZKTestsFor tests which test the general logic of zookeeper related tools, such asRecoverableZooKeeper
, not for tests which depend on ZooKeeper.