Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Date: Tue, 12 Aug 2003 15:37:43 +0100
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: [Testing] New test directory(s)
From: Alex Blewitt <Alex.Blewitt@ioshq.com>
To: geronimo-dev@incubator.apache.org
Content-Transfer-Encoding: 7bit
Message-Id: <8857E8A6-CCD2-11D7-A6C3-0003934D3EA4@ioshq.com>

At present, we only have one test directory in the source code. IMHO we 
need at least two -- one for the unit tests, and one for the 
use-cases/spec-tests.

Ideally code shouldn't get into CVS unless the unit tests run 100%; 
however, (naturally) we'd expect the use-cases to start off at 0% and 
climb ever towards 100% as the lifetime of the project goes on.

Can someone set up the Maven project structure to have the two types of 
test? If we can't have two test directories for source code, then can 
we agree on a naming convention like org.apache.geronimo for unit 
tests, and usecase.Xxx or test.Xxx (such as 
usecase.j2ee.ejb.DeploymentUseCase) to allow the two to be separated?

Also, if use-case tests are going to be different from unit-tests, do 
we want to use/allow a different suffix other than XxxTest.java?

Alex.