[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [stellation-res] Unit test organization
|
> >-----Original Message-----
> >From: stellation-res-admin@xxxxxxxxxxxxxxx
> >[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Mark C.
> >Chu-Carroll
> >Sent: January 11, 2003 11:36 AM
> >To: Stellation-res
> >Subject: Re: [stellation-res] Unit test organization
> >
> >
> >
> >Big +1. This addresses several things that have been concerning me, in
> >good fashion.
> >
> >First, the unit tests are getting confusing. As we add more tests,
> >it's getting harder to find things in the unit test project, and hard
> >to determine what is testing by what suite. Since I expect the number
> >of unit tests to increase dramatically as we work through the upcoming
> >release series, I think that's only going to get worse.
> >
> >Second, I think we have too many projects, which have dependencies that
> >are tricky. Since we'll be switching to Stellation as our primary SCM
> >system very soon, and we don't do subprojects yet, dealing with version
> >consistency is going to become an issue. Keeping the tests in the same
> >projects as the things they test allows us to eliminate one project, and
> >to ensure that the tests and their subjects are always
> >version-consistent.
> >
> > -Mark
> >
Have you considered the possibility of putting the entire Stellation system
into a single Eclipse project. I find that the Eclipse concept of a project
does not bring a lot except if you have peculiar resource or building
requirements. Setting up the system for installation etc. is totally
orthogonal to the Eclipse project organization.
Regards
Jonathan
Personal Email
jgossage@xxxxxxxx
Business email
jonathan@xxxxxxxxxxxxxx
