Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of thehellmaker@gmail.com
 designates 209.85.218.41 as permitted sender)
MIME-Version: 1.0
Date: Sat, 17 Sep 2011 12:09:38 +0530
Message-ID: 
 <CAOTGtFyMsKr16h24G2eb_M=nUzhSRoaMBpKADVzSJiGNu=snjA@mail.gmail.com>
Subject: Running UnitTests before submitting a patch
From: Akash Ashok <thehellmaker@gmail.com>
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=20cf303b3ad3b31f1a04ad1d5f08

--20cf303b3ad3b31f1a04ad1d5f08
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I was just wondering as to how developers go about running unit tests before
they wanna submit a patch. I am not asking about testing the functionality
of the patches, but about the whole suite of regression test cases.

Firstly I end up running the whole suite without a the patch  and second
with patch and compare the results. But it turns out most of the times
there's always inconsistency. Meaning to say a few tests are erratic. The
fail while running the whole suite and pass when run alone. Moreover running
the whole test suite takes about 2 hours.

This is taking a lot of time for me to work on the simplest of the patches.

Could you please share some practices which devs usually follow before
submitting patches? It would be of great help.

Thanks a lot

Cheers,
Akash A

--20cf303b3ad3b31f1a04ad1d5f08--