Re: [Fofredux-devel] unit tests

[Kevin <ke...@dr...>]

> 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.

--=20
Kevin