From: brett l. <bre...@gm...> - 2011-08-08 18:07:12
|
On Mon, Aug 8, 2011 at 10:55 AM, Stefan Frey <ste...@we...> wrote: > I was wondering where to save unit tests with our setup. Usually I prefer the > setup with a folder tree for the sources (src/) and a parallel structure for > the tests (junit/ or test/). > > Is it ok with you (Erik & Brett) to create an additional layer with src/ and > junit/? > The "java way" would be to have our code under net/sourceforge/rails/{game, test, foo} (See also: http://www.oracle.com/technetwork/java/codeconventions-135099.html ) If we're going to add new sub-dirs, we may want to consider moving to the "standard" Java naming conventions. That said, I do prefer to have the tests separate from the regular code base. I don't really care if we call it "test(s)" or "junit" or "unit". I will say that if we call the unit test tree "test", we should remove any other use of that word from the rest of the tree. > EclEmma coverage tool reported an overall code coverage of 40.2% after running > all automated game tests (which is not too bad given that UI and algorithm > packages are not tested by construction, the rails/game package itself has > 73.8% coverage). > > My preferred mock library is JMock, any comments/preferences for this? > JMock is fine by me. > Stefan > > ---Brett |