hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-410) [testing] Speed up the test suite
Date Thu, 15 Oct 2009 00:21:31 GMT

     [ https://issues.apache.org/jira/browse/HBASE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-410:
------------------------

    Attachment: 410-v2.patch

New patch.  Deprecates HBaseTestCase and HBaseClusterTestCase.  Instead, using new utility
class named HBaseTestUtility which will have all you need to test hbase.  I'm starting by
replacing content of the client package with a single junit4 that spins up minicluster on
startup and then runs all tests.  This patch is just a start.

> [testing] Speed up the test suite
> ---------------------------------
>
>                 Key: HBASE-410
>                 URL: https://issues.apache.org/jira/browse/HBASE-410
>             Project: Hadoop HBase
>          Issue Type: Test
>          Components: test
>    Affects Versions: 0.2.0
>            Reporter: Bryan Duxbury
>            Priority: Minor
>             Fix For: 0.21.0
>
>         Attachments: 410-v2.patch, 410.patch
>
>
> The test suite takes a long time to run, and a lot of the time spent running is really
wasted on repeated startup and shutdown, waiting for asynchronous events to occur, and production-tuned
timeouts to occur. Additionally, we use a MiniDFS instead of the local filesystem. 
> We should:
>  - Make whatever changes are needed to the local DFS so that it can run on Windows and
use that as the basis of all of our tests
>  - Minimize redoing expensive setup where possible by combining tests into groups or
suites that can share common setup
>  - Create a way of running all the parts (Master, Regionserver, Client) in a single thread
and explicitly advancing through necessary states so that we can reliably and quickly get
what we need tested accomplished
>  - Use smaller test datasets where it would make a difference (TestTableIndex and TestTableMapReduce,
I'm looking at you!)
> A faster test suite means faster turnaround on new patches, faster Hudson, and a shorter
patch queue. Not to mention less annoyance on the part of the developers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message