Package org.apache.hadoop.hbase.testclassification

package org.apache.hadoop.hbase.testclassification
  • Interfaces
    Class
    Description
    ClientTests
    Tag a test as related to the client.
    CoprocessorTests
    Tag a test as related to coprocessors.
    FilterTests
    Tag a test as related to the org.apache.hadoop.hbase.filter package.
    FlakeyTests
    Tag a test as failing commonly on public build infrastructure.
    IntegrationTests
    Tag 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).
    IOTests
    Tag a test as related to the org.apache.hadoop.hbase.io package.
    LargeTests
    Tagging 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.
    MapReduceTests
    Tag a test as related to mapred or mapreduce.
    MasterTests
    Tag a test as related to the master.
    MediumTests
    Tagging 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'.
    MetricsTests
    Tag a test that covers our metrics handling.
    MiscTests
    Tag a test as not easily falling into any of the below categories.
    RegionServerTests
    Tag a test as related to the regionserver.
    ReplicationTests
    Tag a test as related to replication.
    RestTests
    Tag a test as related to the REST capability of HBase.
    RPCTests
    Tag a test as related to RPC.
    SecurityTests
    Tag a test as related to security.
    SmallTests
    Tagging 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 cluster
    VerySlowMapReduceTests
    Tag a test as related to mapreduce and taking longer than 5 minutes to run on public build infrastructure.
    VerySlowRegionServerTests
    Tag a test as region tests which takes longer than 5 minutes to run on public build infrastructure.
    ZKTests
    For tests which test the general logic of zookeeper related tools, such as RecoverableZooKeeper, not for tests which depend on ZooKeeper.