From: Blair Z. <bl...@or...> - 2004-12-20 21:00:37
|
Bardur Arantsson wrote: > On Mon, Dec 20, 2004 at 10:59:27AM +0100, Nicolas Cannasse wrote: > > >>>>You can download the source from: >>>> >>>>http://www.saunalahti.fi/~jjhellst/extlib/ >>>> >>>>It doesn't have many tests yet, just a few placeholders to demonstrate >> >>the >> >>>>file layout. >>> >>>Ok this looks great. The most important issue right now IMHO is >>>not how the test manager works, but where it lives in CVS. >>> >>>Nicolas said at one stage that the test suite shouldb't be >>>part of the distribution. Whether or not this is the case, >>>I would say it should be easily separable. >>> >>>IMHO test code and library code should be siblings, >>>the tests should be in a subdir of the src (just my opinion). >> >>If Janne or anybody else is willing to take over the test suite CVS >>maintenance, I will give CVS write access. >>As for the repository, I prefer having it in a separate module, so anybody >>checking out extlib sources does not automaticaly get test suite too. >>Something like : >> >>/CVSROOT >>/extlib-dev >>/extlib-test >> > > > I'm wondering why you'd prefer to keep them separate... > Does it provide any tangible benefits? > > (It certainly does have the drawback of making it more > cumbersome to keep the test suite and the library in > sync.) I agree that the two should be kept together to support code coding. Any additional steps that a developer has to do to check their new code just gets in the way, even if it's done only once. As practice, I don't think I know of any package that has a test suite that doesn't ship with it. Most GNU software has a make test that you can run after you build it. Regards, Blair -- Blair Zajac <bl...@or...> Plots of your system's performance - http://www.orcaware.com/orca/ |