Re: [Fofredux-devel] unit tests

[Andrew T. (nilspace) <nil...@us...>]

branching is not a good idea. it doesn't promote keeping them
together. Putting them in another directory is the best way to do it
then. That way, when we do branch/tag the FoFR code, the tests will
also be tagged/branch.

Andrew

On 12/5/05, Kevin <ke...@dr...> wrote:
>
> > Well, you could add a new project in the CVS repository -
> > fofredux-test or something similar. Anyone could check out the
> > fofredux project, and devs could subsequently checkout fofredux-test:
> >
> > cvs -d:ext:nil...@cv...:/cvsroot/fofredux co fofredux
> > cvs -d:ext:nil...@cv...:/cvsroot/fofredux co fofredux-test
>
> The unit tests should evolve as the code does.  They should be tagged and
> branched to follow the code that they test.  Wouldn't putting the unit
> tests in their own module hinder this?
>
> Writing, running, and maintaining the unit tests should be made as easy a=
s
> possible.  Otherwise, they won't get used.  That's why my first thought
> was making it a subdirectory and just excluding it when creating tarballs
> for release.
>
> --
> Kevin
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&opclick
> _______________________________________________
> Fofredux-devel mailing list
> Fof...@li...
> https://lists.sourceforge.net/lists/listinfo/fofredux-devel
>