[ 
https://issues.apache.org/jira/browse/HBASE-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030021#comment-13030021
 ] 

stack commented on HBASE-2675:
------------------------------

Is the following enough?

{code}
mvn clean test -Dtest=TestFromClientSide
{code}

It excercises the UI from the client side -- it starts up a minicluster -- 
doing about 40 odd little tests.

> Quick "smoke tests" testsuite
> -----------------------------
>
>                 Key: HBASE-2675
>                 URL: https://issues.apache.org/jira/browse/HBASE-2675
>             Project: HBase
>          Issue Type: Test
>            Reporter: Benoit Sigoure
>            Priority: Minor
>
> It would be nice if there was a known subset of the tests that run fast (e.g. 
> not more than a few seconds) and quickly help us check whether the code isn't 
> horribly broken.  This way one could run those tests at a frequent interval 
> when iterating and only run the entire testsuite at the end, when they think 
> they're done, since doing so is very time consuming.
> Someone would need to identify which tests really focus on the core 
> functionality and add a target in the build system to just run those tests.  
> As a bonus, it would be awesome++ if the core tests ran, say, 10x faster than 
> they currently do.  There's a lot of "sleep"-based "synchronization" in the 
> tests and it would be nice to remove some of that where possible to make the 
> tests run as fast as the machine can handle them.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to